Noetic Kick-off and Release Checklist

[sloretz]

This ticket is for things that need to be done for the May 2020 ROS 1 Noetic release. Copied from the Melodic Release ticket and Melodic Kick-Off Checklist.

Prerequisites

• Python 3 support for Melodic checklist (Melodic Python3 support tracking issue #17898)
• Resolve how to do rosdep keys for python 3
  • some discussion here
• Update and release rep-151 with python3 plan (REP 151 Python 3 rewrite ros-infrastructure/rep#201)

Kickoff part 1

• Choose distribution name: Noetic Ninjemys
• Commission a logo
• Commission a turtlesim icon
• Add to REP3 with proposed platforms and minimum requirements, request feedback from community (Update REP 3 for Noetic Ninjemys ros-infrastructure/rep#202)
• List on ROS wiki with expected release date
  • http://wiki.ros.org/Distributions
  • see example
  • http://wiki.ros.org/action/info/Distributions?action=diff&rev2=102&rev1=99
  • Wiki page for noetic: http://wiki.ros.org/noetic

Ubuntu buildfarm setup

• Create [email protected]
• Add Ubuntu 20.04 to bootstrap repository on repos.ros.org
  • see example
  • actual: Add focal to list of distros ros-infrastructure/reprepro-updater#72
• Add Ubuntu 20.04 to buildfarm_deployment_config
  • note this is not the live one, it's for reference only
  • see example
  • actual: Add focal to list of distros ros-infrastructure/buildfarm_deployment_config#52
• Add Ubuntu 20.04 to ros_buildfarm/common.py
  • see example
  • actual: Add focal to OS code name mapping ros-infrastructure/ros_buildfarm#699

Python Dependencies setup

• Check that all python packages and scripts below work with python 3.7 and 3.8
  • catkin_pkg
  • rospkg
  • rosdistro
  • rosdep
    • Py 3.7 + 3.8 CI Add Python 3.7 and 3.8 to test matrix ros-infrastructure/rosdep#735
  • vcstools
  • wstool
  • rosinstall
  • bloom
  • rosinstall_generator
  • osrf_pycommon
  • catkin_tools
  • vcstool
  • ros_release_python
• Add newly supported platforms to list of platforms for each Python package (in stdeb.cfg), in order of dependency
  • do this as soon as debs for new Ubuntu are available, in pre-alpha!
  • catkin_pkg
    • Example (Melodic: Add bionic to the list. ros-infrastructure/catkin_pkg#198)
    • Actual: Add a Suite3 option with Ubuntu Focal. ros-infrastructure/catkin_pkg#271
  • rospkg
    • Example (Melodic: Add bionic. ros-infrastructure/rospkg#123)
    • Actual: add Suite3 including Focal ros-infrastructure/rospkg#184
  • rosdistro
    • Example (Melodic: Add bionic. ros-infrastructure/rosdistro#108)
    • Actual: add Suite3 including Focal ros-infrastructure/rosdistro#148
  • rosdep
    • Example (Melodic: Add bionic. ros-infrastructure/rosdep#567)
    • Actual: Add Suite3 option with Ubuntu Focal ros-infrastructure/rosdep#734
  • vcstools
    • Example (Melodic: Add bionic. vcstools/vcstools#127)
    • Actual: Add Suite3 option with Ubuntu Focal vcstools/vcstools#159
  • wstool
    • Example (Melodic: Add bionic vcstools/wstool#115)
    • Actual: Remove old platforms from py2 release, add Suite3 for Ubuntu Focal vcstools/wstool#148
  • rosinstall
    • Example (Melodic: Add in bionic. vcstools/rosinstall#113)
    • Actual: Remove old platforms from py3 release, add Suite3 option with focal vcstools/rosinstall#122
  • bloom
    • Example (Melodic: Add bionic. ros-infrastructure/bloom#452)
    • Actual: Add Suite3 option with Ubuntu Focal ros-infrastructure/bloom#558
  • rosinstall_generator
    • Example (Melodic: Add bionic. ros-infrastructure/rosinstall_generator#42)
    • Actual: Add Suite3 option with Ubuntu Focal ros-infrastructure/rosinstall_generator#62
  • osrf_pycommon
    • Example (Melodic: Add artful and bionic. osrf/osrf_pycommon#45)
    • Actual: Remove old py2 platforms, add Suite3 option with Ubuntu Focal osrf/osrf_pycommon#58
  • catkin_tools
    • Example (Melodic: Add bionic. catkin/catkin_tools#497)
    • Actual: Remove old platforms from Py2 release, Add Suite3 option for Ubuntu Focal catkin/catkin_tools#589, Update release suites. catkin/catkin_tools#564
  • vcstool
    • Example(Melodic: dirk-thomas/vcstool@dcee1a0)
    • Actual: add Suite3 including Focal dirk-thomas/vcstool#112
• Use ros_release_python
  • Goal is to make the currently released versions available in the new distros using the --include option

---

• create Docker images for the new platforms in rep 3 for all targets
  • See example
  • actual: Add ubuntu focal docker images osrf/multiarch-docker-image-generation#32

---

• Create distribution files in ros/rosdistro
  • Example
  • Actual: add source entries for most ROS core packages for Noetic #21988
• create new mailing list for buildfarm emails
  • Example
  • Use same settings as the existing ones (need to get admin on an older group to see settings)
  • Actual: https://groups.google.com/forum/#!forum/ros-buildfarm-noetic
• Add ros_buildfarm_config entries
  • Example
  • Actual: Add Noetic doc/source/release jobs ros-infrastructure/ros_buildfarm_config#157
• Generate new management jobs
• generate new sync-packages-to-{testing,main} jobs
  • Run this script

Prerelease Website

• Release the catkin
  • Needed for prerelease website testing
  • Example
  • Actual: Release Catkin 0.7.20 to Noetic #23421
• Add new column in for the new distro with theme and placeholder image
  • Example
  • actual: Add Noetic to Prerelease website ros-infrastructure/prerelease_website#59 Add actual ROS Noetic logo ros-infrastructure/prerelease_website#60
• Make Ubuntu 20.04 the preferred OS
  • Example
• Test prerelease process (except for latest ubuntu distros)

Pre-release documentation

• Add Noetic button to the wiki Add noetic to list of distros ros-infrastructure/roswiki#298
• Add standard distribution wiki pages (planning, migration, etc...)
  • http://wiki.ros.org/noetic/
  • http://wiki.ros.org/melodic/Planning Appears unused in melodic, did not create Noetic equivalent
  • http://wiki.ros.org/noetic/Migration
  • http://wiki.ros.org/melodic/Planning/Maintenance
    • link to the blocked releases status page rather than using a static page
    • update previous distributions Maintenance pages accordingly
  • http://wiki.ros.org/noetic/Installation
    • Create main page http://wiki.ros.org/noetic/Installation
    • Create Platforms
    • Create DebianSources
    • Create DebEnvironment
    • Create PostInstall
    • All of the below should have a warning about distribution pending like this
    • Create Ubuntu
    • Create Debian
    • Create Source

Low level releases

• Release ros-core packages
  • ros_environment
  • rosbag_migration_rule
  • roscpp_core
  • genmsg
  • gencpp
  • geneus
  • genlisp
  • gennodejs
  • genpy
  • message_generation
  • message_runtime
  • ros_comm_msgs
  • std_msgs
  • cmake_modules
  • rospack
  • ros
  • ros_comm
  • rosconsole_bridge
  • common_msgs
  • ros_tutorials
    • re-release as soon as the turtle is available (Add noetic turtle ros_tutorials#85)
  • roslisp
• Release ros-base packages
  • actionlib
  • angles
  • bond_core
  • dynamic_reconfigure
  • class_loader
  • pluginlib
  • nodelet_core
• common_tutorials

Early Buildfarm

• Create Migration page
  • http://wiki.ros.org/noetic/Migration
• Announce availability of the build farm
  • Example
• Ping all maintainers of packages in desktop-full

Day prior and day of Release

• Announce logo design and kick off t-shirt campaign*

ROS Wiki

• make this the default distro
  • example
  • actual: Make Noetic default distro ros-infrastructure/roswiki#302
• Update Version macro from “Expected in distroX” to “distroX”
• Manually redeploy wiki once finished by pulling repo and restarting Apache instance
  • roswiki checkout lives in /var/www/wiki.ros.org/data/plugin
  • restart apache with script in /home/ros/reload_httpd
• Update symlink for default API doc:
  • /home/rosbot/docs/api → /home/rosbot/docs/distroX/api
  • /home/rosbot/docs/latest → /home/rosbot/docs/distroX
  • (if this is an LTS) /home/rosbot/docs/latest-lts -> /home/rosbot/docs/distroX
• Update http://wiki.ros.org/ROS/Installation to point to distroX
• Update verbiage on these wiki pages, e.g. 'upcoming release' vs. 'current release'
  • http://wiki.ros.org/noetic/Installation
  • http://wiki.ros.org/noetic
  • http://wiki.ros.org/Distributions

ROS browse

• update default distro
  • Example
  • actual: Make Noetic default distro ros-infrastructure/rosbrowse#9

ROS docker images

• add Dockerfiles to create ROS docker images

Misc Infra

• Update www.ros.org bottom row widget to point to new release with logo
• Update www.ros.org/install to point to new release with logo
• Create Release category on Discourse
  • Example
  • actual: https://discourse.ros.org/c/release/noetic/66
• Update mirror documentation
  • Example
• update ros mirrors
  • Example
• update osrfoundation mirrors
  • Must wait until there are builds for ignition and gazebo for all supported platforms
• Add Noetic to high level page http://wiki.ros.org/Installation/Ubuntu
• Add Noetic to index.ros.org (Add ROS Noetic to list of ROS distros ros-infrastructure/rosindex#231)

Communication

• Announcement pointing to migration guide
  • Post to discourse
  • Post to blog
  • Post to G+
  • Post to Twitter

[nuclearsandwich]

* Goal is to make the currently released versions available in the new distros using the `--include` option

The --include option wasn't updated to support the new aptly-based bootstrap repository. I've opened ros-infrastructure/ros_release_python#31 to track support for it and am hoping to tackle it well before it's needed.

[SteveMacenski]

It looks like python-catkin-pkg in Focal is missing from the python file, which blocks geographic_info. I can force release it but I feel like that should probably be fixed beforehand.

Thoughts?

[sloretz]

It looks like python-catkin-pkg in Focal is missing from the python file, which blocks geographic_info. I can force release it but I feel like that should probably be fixed beforehand.

@SteveMacenski In ROS Noetic geographic_info should depend on the Python 3 equivalent python3-catkin-pkg instead. Further, if doesn't need the CLI tools then it should depend on python-catkin-pkg-modules in Melodic and earlier, and python3-catkin-pkg-modules in Noetic.

[SteveMacenski]

Ah ok. I'm not a python user in general so I'll probably need someone to sanity check it for me that everything's been properly updated. I did a glance over it and the obvious things I'm aware of from 2.7-3.4 look to be done already.

If that's the case, I can update that stuff and ship it out

[clalancette]

@sloretz Should we close this out now that Noetic has been released?

[clalancette]

I'm going to go ahead and close this now that Noetic is released. Feel free to reopen if needed, or open up follow-up tasks.