On Wed, Sep 5, 2018 at 12:56 PM Tomasz Torcz <tomek@xxxxxxxxxxxxxx> wrote:
On Wed, Sep 05, 2018 at 10:15:26PM +0530, Parag Nemade wrote:
> >
> > I'd be *strongly* disinclined to give a Freeze Exception for a GNOME
> > mega-update. There's just far too much that could go wrong. Please plan to
> > land the mega-update in updates-testing once the Freeze lifts. U-T is
> > enabled by default on the Beta, so people will pick it up on their first
> > post-install update anyway.
> >
> >
>
> Please don't stop this update. There will be few required fixes in this
> megaupdate which we need early to test.
Can you get exceptions for specific packages fixing specific bugs?
Of course, that's what the Freeze Exception process is for. Propose a bug as a blocker or freeze exception using https://qa.fedoraproject.org/blockerbugs/propose_bug
Now, let's talk frankly about what a "freeze" is, because I think that a lot of people on this thread don't understand what it means. A freeze (in Fedora parlance) means that we stop pushing Bodhi updates to the stable "fedora" repository for a few weeks while we stabilize a Beta or GA release.
The freeze dates are clearly announced at the start of each Fedora cycle (usually just after the previous release branches off). In the case of Fedora 29, those dates could be found at https://fedoraproject.org/wiki/Releases/29/Schedule
Once we enter Freeze, we only allow changes in that fix bugs declared to be Blockers or Freeze Exceptions. Blockers are fairly obvious: if the bug causes Fedora to fail one or more blocking release criteria, it's a blocker bug.
Freeze Exceptions have slightly slushier rules, but they generally amount to this: "In general, freeze exception bugs are usually bugs for which an update is not an optimal solution, and for which the fix is reasonably small and testable (this consideration becomes progressively more important as a release nears, so bugs may be downgraded from freeze exception status late in the release process if it transpires that the fix is complex and hard to test)."
Rebasing an entire desktop environment is *not* a small change. It is likely to introduce new blocking issues and is (to my mind) an unreasonable request at this stage of the process. I can be overruled on this (I'm only one vote on the Blocker/FE process crew), but I don't think it's wise to do this more than a week into a Freeze.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
