On Mon, Jul 26, 2021 at 10:07 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > On 23. 07. 21 19:27, Ben Cotton wrote: > > Hi everyone, > > > > A few years ago, I created release schedules[1] through Fedora Linux > > 36. We've almost used up that buffer, so it's time to create the next > > few years worth of schedules. Before I start that, I want to take the > > opportunity to make sure the schedules match reality. > > > > For teams that already have tasks on the release schedules, I have > > opened issues in the schedule repo[2]. Please use those to let me know > > what changes make sense. You may also be hearing from members of the > > Program Management team about those soon. If your team is not > > represented on the release schedule but you think it would be, file a > > new issue. > > Hey Ben, > > Do you think it makes sense to include expected Python releases there? > > With the annual release schedule we can predict that the Python mass rebuild > will happen at the May/June boundary every year in all odd-numbered Fedora > releases. > We could also include things like compiler toolchains (GCC/LLVM), KDE Plasma, GNOME, etc. which are major integration points with predictable schedules. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
