I am generally +1 to this. I suspect we need to revisit many of the subteam tasks lists to see if they are still valid.

Agreed. I plan on approaching all of the sub teams and evaluating the current state of their tasks for the F31 schedule. The basic schedule hasn't changed much in the nine years I've been around, so it's probably worth an in-depth review.

What Bex said.

If we approve this now, we preclude any new Objectives that may wish to alter the F30 schedule. Given some of the talks at Flock, are we confident we don't want to entertain any discussion of delaying or extending the development cycle?

LGTM .

Just one feedback for revisiting the sub-tasks and analyze if we drifted from the actual schedule in past for any specific one and if there is a need for the current release to increase/decrease the time-line accordingly for any particular sub-task.

and thanks for working on it.

I'm open to delaying the approval of this schedule if Council and FESCo are both on board. I don't think there's any particular need to adopt the N+1 schedule this early in the N development cycle (other than the rawhide branching makes a convenient point to start thinking about the next release.)

That said, from reading the documentation, I wonder if proposal and acceptance/rejection of Objectives should be an explicit part of the schedule. Ditto for review of the objectives (i.e. determining when an Objective is complete (or should be dropped). That might be a matter for separate discussion)