The GNOME 43 release schedule is here:

https://wiki.gnome.org/FortyThree

The important dates are

• July 2: GNOME 43.alpha
• August 6: GNOME 43.beta
• September 3: GNOME 43.rc
• September 21: GNOME 43.0

Tentative F37 schedule:

• 6 August - GNOME 43 beta and UI freeze
  • Tasks:
    • Check that GNOME modules all have releases
    • Update packages with the beta release
    • Notify QA when the beta release is available in Fedora
    • Plan test day to coincide with GNOME beta availability
• 15 August - GNOME test week should be happening
• 13 September: F37 beta
  • Tasks:
    • Review package set and image size
    • Start planning release marketing
    • Add upgrade artwork to gnome-software
• 21 September: GNOME 43.0 release
  • Tasks:
    • Check that all GNOME modules have releases
    • Packages to be updated
    • Notify QA when 43.0 is available
• 3 October: F37 final freeze
  • Task: start rolling out GNOME 43.0 Flatpak updates
• 18 October: F37 early target date
  • Tasks:
    • Publish "what's new in F37 workstation"
    • Update website screenshots

It would be good to agree ahead of time who is going to do each of these tasks.

We could update the template schedule with some of these extra items, so it looks like this:

Week    Milestone
1   Fedora cycle start
2   
3   
4   
5   
6   
7   
8   
9   
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  System-wide change proposal deadline
21  Self-contained change proposal deadline
22  
23  
24  
25  
26  GNOME Beta (UI Freeze) - 1. check that all GNOME modules have releases, 2. update packages with the GNOME beta, 3. notify QA when the GNOME beta is available in Fedora, 4. plan a test day to coincide when the beta is available (~2 weeks after GNOME beta release)
27  Fedora branch from rawhide
28  GNOME test week (2 weeks after GNOME beta)
29  
30  GNOME RC
31  
32  Fedora Beta - 1. review package set and image size, 2. start planning marketing, 3. add upgrade artwork to gnome-software
33  GNOME stable release - 1. update packages with the new GNOME release, 2. notify QA when the update is complete, 3. start preparing GNOME Fedora Flatpak updates
34  
35  Fedora Final Freeze. Start distributing GNOME Fedora Flatpak updates (should happen 2 weeks prior to expected release date)
36  
37  Fedora Early Target Date - on release publish "what's new" post, update website content
38  
39  

Adding the meeting tag so the group can review this.

The working group discussed this at yesterday's meeting. The schedule looks OK, though it needs to be noted that the GNOME release dates are when tarballs are due - there's no specific date when each milestone is released - it becomes available in the weeks following each deadline.

Actions are now to:

1. update our schedule
2. inform sumantro about the expected window in which GNOME testing will need to take place
3. identify the best way to update QA about future scheduling changes

The schedule has been updated: https://docs.fedoraproject.org/en-US/workstation-working-group/schedule/