Formalize & allocate the task to create new branches for new releases?
Forgetting the creation of new branches if no one is responsible can undermine collaboration and hinder other people’s work. (e.g. using tickets (i.a. as reminder), early allocation, determine someone to put it into their calendar, …): Fedora Linux 37 Schedule: Docs - release-notes#883
If there is time left, it would be interesting to know if there is a consensus to proceed with (so, to test) the current approach of the maintenance strategy of the Workstation & Spins guide before I proceed with writing and tailoring the guide with this approach in mind; or if we need to discuss first how to proceed.