Hi everyone,

Here's a quick overview of some particular dates of interest in the
F42 release cycle, which can also be found in the F42 release
schedule[1]:

Now - we are in Final Freeze
April 10 - F42 Final Go/No-Go meeting[2]
April 15  - Current (early) final target release date
April 24 - Elections Nominations open for x2 Council seats, x4 FESCo
seats and x4 Mindshare Committee seats
May 13 - F40 is EOL
May 19 - Elections Voting opens
May 30 - Elections Voting closes & results follow


For those of you already looking ahead to F43, please take note of the
following dates, which can also be found in the F43 release
schedule[3]:

June 25 - Changes requiring infrastructure changes submission deadline
July 1 - System Wide changes and those requiring mass rebuild
submission deadline
July 22 - Self Contained changes submission deadline
July 23 - Mass rebuild
August 12 - F43 branching


Please keep an eye out for updates to our F42 Go/No-Go meeting event.
Currently it is scheduled for Thursday, April 10 @ 1700 UTC in the
#fedora-meeting room on Matrix. A reminder or a rescheduling email
will be sent on Wednesday, April 9 in advance of this meeting, pending
the availability of a suitable release candidate.




Kindest regards,
Aoife

[1] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html
[2] https://calendar.fedoraproject.org/meeting/11013/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html


-- 

Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to