On 17 November 2017 at 13:30, Randy Barlow <randy(a)electronsweatshop.com> wrote:
Greetings fellow Fedorans!
During today's FESCo meeting[0], there was discussion around a proposal
to increase the freeze period from 2 weeks to 3 weeks[1]. Several
members of FESCo thought this proposal might be unpopular with Fedora
developers, so a compromise proposal was made: increase the beta freeze
to 3 weeks, but keep the stable freeze at 2 weeks[2].
We would like to ask for feedback from the Fedora community about this
proposal. Feel free to reply here, or comment on the FESCo ticket.
Thanks in advance for your thoughts!
How many of the last "long" freezes have happened because of bad
software and how much has happened because other issues caused
composes to actually test not to be created? We "seem" to spend a lot
of the freeze working for an actual working compose before we can
actually see what is going on in with the software that people want.
Would it make more sense to just have the Freeze not start until we
have a bootable compose? [I realize this is a overflowing stack
recursive loop if not defined adequetely define bootable but if QA
can't test an install until week 2 of the freeze.. we weren't ready to
freeze for packages.
[0]
https://meetbot.fedoraproject.org/fedora-meeting/2017-11-17/fesco.2017-11...
[1]
https://pagure.io/fesco/issue/1790
[2]
https://pagure.io/fesco/issue/1790#comment-480090
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
--
Stephen J Smoogen.