Create detailed release plan

[clalancette]

No description provided.

[clalancette]

Create a detailed plan for the release team to follow.

This will generally lay out the release week-by-week, starting with the last week of March. For each week, certain tasks need to be completed, and someone from the release team should be assigned to each task.

The breakdown looks something like this:

Week of March 25 - March 29:

• Fix flaky tests on nightly: https://ci.ros2.org/view/nightly/
• Update vendored packages
• Review incoming PRs (feature freeze hasn't happened yet, so this is shepherding the last of the features in)

Week of April 1 - April 5

• Fix flaky tests on nightly: https://ci.ros2.org/view/nightly/
• Update vendored packages
• Review incoming PRs
• Finalize manual testing tickets (use YATM to generate the test cases)

Week of April 8 - April 12

• RMW freeze
• Release rolling branches into Rolling
• Initial smoke testing
  • Test that the debs work for basic things
  • Test that the “archives” work on Linux, Windows
• Fix flaky tests on nightly: https://ci.ros2.org/view/nightly/

Week of April 15 - April 19

• Announce overall freeze + upcoming tutorial party
• Release rolling branches into Rolling again
• Branch from rolling
  • Branch ros2.repos
  • Create source branches for iron in core repos
  • Create iron/distribution.yaml in rosdistro
  • Add distro to https://ci.ros2.org/
  • Update branches in distribution.yaml to point to 'iron' branch
  • Update tracks.yaml in the release repositories to correspond to distribution.yaml
  • rolling branches are now open again
• Try to build the ros1_bridge against upstream Ubuntu ROS 1 packages
• Fix flaky tests on nightly: https://ci.ros2.org/view/nightly/
• Tickets from Iron board

Week of April 22 - April 26

• Add distro to documentation
• Create interim tarballs for testing
• Announce branch, beta and tutorial party
• Look at test failures
  • On the buildfarms (CI and build) and try to get us to green
• Review outstanding PRs (only non-API breaking bug fixes at this point)
• Manual testing
• Reach out to Tully regarding T-Shirt campaign

Week of April 29 - May 3

• Manual testing
• Documentation
  • Short-form Features, API changes
  • Long-form Changelog entries for all of ROS 2
  • Demos for each of the features on the short-form list
• Look at test failures (low priority)
  • On the buildfarms (CI and build) and try to get us to green
• Investigate problems found during manual testing

Week of May 6 - May 10

• Kick-off T-spring campaign
• Documentation
  • Short-form Features, API changes (see here)
  • Demos for each of the features on the short-form list
• Look at test failures
  • On the buildfarms (CI and build) and try to get us to green
• Investigate problems found during manual testing
• Review outstanding PRs (only non-API breaking bug fixes at this point)

Week of May 13 - May 17

• Final round of releases into Iron
• Final touches on release documentation
• Look at test failures
  • On the buildfarms (CI and build) and try to get us to green
• Investigate problems found during manual testing
• rosdistro freeze for Iron

Week of May 20 - May 23

• Release!