On Fri, 2019-11-08 at 07:20 -0800, Kevin Fenzi wrote: > On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote: > > On 07. 11. 19 18:35, Ben Cotton wrote: > > > Here's the link to the Community Blog post that looks at the > > > schedule options: > > > https://communityblog.fedoraproject.org/accommodating-flock-in-the-release-schedule/ > > > > From the post: > > > I’m inclined to go with option 0, plus a brief freeze after > > > branch. > > > > This seems like best option to me as well. > > Yeah, same here. > > kevin Ben, thanks a lot for your post. It's great summary of our possibilities! I agree with you in general but I don't like the `brief` wording here. What that means exactly? I would rather go with specifying a strong freeze. Meaning that the freeze will continue until compose is available. What do you think? Jirka > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
