>>> On 11/25/2016 05:51 PM, Peter Robinson wrote: >>> >>>> So we already do pretty much what you outline above. I started the >>>> first push to f25-updates on the Friday before the release. >>> >>> >>> I think, we are talking past each other. >>> >>> You seem to be referring to "the freeze" in terms of the final release >>> push, while I am talking about what you'd probably call alpha or beta >>> stage. >>> >>> Actually, I am referring to the stage of the release preparations, when >>> rel-eng stops pushing packages from "update-testing" to "main". >> >> >> That only stops at the Final freeze point. After Final freeze, only >> freeze exception / blocker bug fixes are pushed to what you call >> 'main'. > > OK. This is the harmful stage, I am talking about. > > I think this stage is fundamentally flawed and needs to be redesigned. > > To provide so detail about this harm: > > I have been trying to push a package chain consisting of 2 new packages, > which are required to update a 3 package, to Fedora: > > The first package hit "the freeze". It took ~3 weeks to make it to fc25 > stable. The second package could not be built before the first packages was > in fc25. It was build when the freeze was lifted, summing up to an overall > delay in order of 4-5 weeks. IIRC, the 2nd package is stuck in > updates-testing. A new package can be tagged into build override just like any other. If you did that you could have then build the subsequent packages and submitted them as an update together which would then go to testing in a few days for people to be able to consume. If you then felt they should have gone stable earlier there's the freeze exception process for exactly that, else they would have gone out before release as a "zero day" update. > Of course the fc23/fc24 have been release. Yes, but ultimately they're independent releases and the only time there might be a slight issue is when in freeze and upgrading between releases during that time and there's distro-sync that will deal with that just fine. Peter _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
