On Fri, 2018-02-16 at 09:54 +0100, nicolas.mail...@laposte.net wrote: > > ----- Mail original ----- > De: "Adam Williamson" > > Hi Adam > > > This is...pretty much what I do for every release, and have been doing > > since like Fedora 14 or something? > > You do it end of cycle,
No I don't. I do it throughout the cycles. I tagged the first F28 Beta blocker on 2017-11-27: https://bugzilla.redhat.com/show_bug.cgi?id=1496562 which was actually a bit late, historically speaking; we frequently file blockers for N+1 before N comes out. We specifically create the blocker bugs two releases in advance so this is always possible. > and it is awe-inspiring to see you trying to fix all the problems > that accumulated since the next-to-last branching at once, This is not at all what happens. We constantly work on this throughout the cycle. What you see at the end of the cycle (when I start sending out mails to devel@) is just what's left at that point in time. If you follow the process via the tracker bugs or the blocker review meetings, you will see that we are constantly working on this process, it never stops. If you hang out in #fedora-releng for a while you will see that we generally work on fixing broken composes (Rawhide, Branched and post-release stable) all the time as well. > but maybe some attention before the errors hit the fan and you have > to intervene would help you? > > Right now rawhide has to be *very* broken for it to get any attention. No it does not. This is not true. Rawhide is tested every day and I (and several others) pay attention to the results and attempt to get bugs fixed as quickly as possible. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
