-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add preliminary timeline for Galactic #868
Conversation
Signed-off-by: Scott K Logan <[email protected]>
Signed-off-by: Scott K Logan <[email protected]>
Would it be valuable to include the duration of each window along with the dates? |
Signed-off-by: Scott K Logan <[email protected]> Co-authored-by: Chris Lalancette <[email protected]>
Signed-off-by: Scott K Logan <[email protected]>
Signed-off-by: Scott K Logan <[email protected]>
Signed-off-by: Scott K Logan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have one minor thing that we could consider moving. Otherwise, I think the 9 week timeline, with 7 weeks of feature freeze, seems reasonable to me. @ros2/team please comment on your thoughts on this timeline.
Freeze rosdistro. | ||
No PRs for Galactic on the ``rosdistro`` repo will be merged (reopens after the release announcement). | ||
|
||
Sun. May 23, 2021 - General Availability |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One potentially controversial thing; what if we move this to Monday, May 24? I know its not World Turtle Day anymore, but at least we won't be working on a weekend :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the idea is that it's actually on May 21st, and the 22nd and 23rd are just to let debs catch up if needed. So the only work to do on Sunday is to send the discourse post (which should have been drafted the week before).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All right, that works for me.
I'm going to go ahead and merge this; if we decide we need to change the timeline further, we can do a follow-up. |
This is the same timeline discussed during the ROS 2 meeting, and includes the 1 week bump in the duration of the freeze event and the addition of a preliminary "alpha" window for Linux-only testing prior to branching from Rolling.