Il mer 8 nov 2017, 16:45 Ivan Kelly <iv...@apache.org> ha scritto: > > This has been done deliberately. Like for 4.5.0. > > I am ok if you PMC want to do it differently. > > Or maybe I have misunderstood the guide. > > You already stated this on slack. I apologize I went forward following > the > > guide > Oh, I'm misremembering how we used to do it, another project I worked > on had it different. > > However, the point still stands. The final release should have a > different sha1 than the candidates, otherwise people's maven caches > get messed up, leading to hidden problems down the line. >
I think that people who tests an rc should be able to clean up their own local repo. Rcs are not tested on CI or other automatic systems. Anyway this is just my opinion, I am open to whatever convention. Enrico > > >> I ran the tests twice, and both times the following failed for me. > >> They're probably flakes, but they failed on 2/2 so they should be > >> investigated. This is on a machine that sometimes runs master tests > >> cleanly (we really need to sort out our flakes). > >> - BookKeeperAdminTest.testDecommissionBookie > >> - > >> > TestRackawareEnsemblePlacementPolicyUsingScript.testNewEnsembleWithEnoughRacks > >> - BookKeeperDiskSpaceWeightedLedgerPlacementTest > >> > > > > Ok let's dig into this. > It would be good for others to confirm whether they see the same > failures, even if only periodically. > > -Ivan > -- -- Enrico Olivelli
