Here’s the agenda for the meeting 2022-10-05T18:30:00Z in #fedora-meeting-1:
- Action item followup
@ankursinha’s improvements for the preview.sh/build.sh
discussion topic - Merge request
- 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
- Your topics here!
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.
Minutes and full logs are available.
- We agree to use Gitlab issues & milestones to track key actions required for the upcoming releases (release schedule)
- pboy to test run the new builder script on Mac
- py0xc3 to create tickets on Gitlab to track the required tasks for next release
I created tickets for those tasks that could be a “blocker” in some circumstances for other contributors’ work.
Feel free to review the tasks and the respective milestones that I have chosen.
The “Add new tickets for the next release” ticket already contains the list of what to create for the next release.