Melodic Kick-Off Checklist

[clalancette]

This is a checklist of things to do for the Melodic kick-off (pre development and development) (copied from #13550):

• Choose distribution name: Melodic
• commission a logo @tfoote
• Add to REP3 with proposed platforms and minimum requirements, request feedback from community (Melodic: Update REP3 for Melodic Morenia ros-infrastructure/rep#139)
  - [ ] Add ament to the "Build System" section of REP3 PR if we decide to do ament in ROS1
• List on ROS wiki with expected release date (see http://wiki.ros.org/action/diff/Distributions?action=diff&rev1=80&rev2=81 for an example on how to do this)
• Add Ubuntu Artful + Ubuntu Bionic to bootstrap repository on repos.ros.org (Melodic: Add in bionic to the list of distros. ros-infrastructure/reprepro-updater#51)
• Add Ubuntu Artful + Ubuntu Bionic to buildfarm_deployment_config (note this is not the live one, it's for reference only) (Melodic: Add in bionic support. ros-infrastructure/buildfarm_deployment_config#22)
• Add Ubuntu Artful + Ubuntu Bionic to ros_buildfarm/common.py (Melodic: Add in artful and bionic to the short os names. ros-infrastructure/ros_buildfarm#493)

---

• 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 (Melodic: Add bionic to the list. ros-infrastructure/catkin_pkg#198)
  • rospkg (Melodic: Add bionic. ros-infrastructure/rospkg#123)
  • rosdistro (Melodic: Add bionic. ros-infrastructure/rosdistro#108)
  • rosdep (Melodic: Add bionic. ros-infrastructure/rosdep#567)
  • vcstools (Melodic: Add bionic. vcstools/vcstools#127)
  • wstool (Melodic: Add bionic vcstools/wstool#115)
  • rosinstall (Melodic: Add in bionic. vcstools/rosinstall#113)
  • bloom (Melodic: Add bionic. ros-infrastructure/bloom#452)
  • rosinstall_generator (Melodic: Add bionic. ros-infrastructure/rosinstall_generator#42)
  • osrf_pycommon (Melodic: Add artful and bionic. osrf/osrf_pycommon#45)
  • catkin_tools (Melodic: Add bionic. catkin/catkin_tools#497)
  • vcstool (Melodic: dirk-thomas/vcstool@dcee1a0)
• Use ros_release_python to make the currently released versions available in the new distros. Use the --include option

---

• create Docker images for the new platforms (Ubuntu Artful + Ubuntu Bionic) for all targets Add in artful and bionic. osrf/multiarch-docker-image-generation#10

---

• Create distribution files in ros/rosdistro (Melodic: Add melodic. #16687)
• add ros_buildfarm_config melodic entries (Melodic: Add melodic. ros-infrastructure/ros_buildfarm_config#102)
  • create new mailing list (https://groups.google.com/forum/#!forum/ros-buildfarm-melodic) with exactly the same settings as the existing ones (need to get admin on an older group to see settings)
• generate new management jobs (see https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/deploy_configuration.rst)
• generate new sync-packages-to-{testing,main} jobs for Melodic by running this script: https://github.com/ros-infrastructure/ros_buildfarm/blob/master/scripts/release/generate_release_trigger_upload_jobs.py

---

• Release catkin into Melodic (prerequisite for prerelease website testing) (Lunar: ros-gbp/catkin-release@a62289f)

---

• prerelease website
  • Add new column in for the new distro with theme and placeholder image (Melodic: Melodic ros-infrastructure/prerelease_website#47)
  • Add new LTS distros as preferred (Melodic: Melodic ros-infrastructure/prerelease_website#47)
  • Make Ubuntu Bionic the preferred OS (Melodic: Make bionic "recommended". ros-infrastructure/prerelease_website#52)
  • Test prerelease process (except for latest ubuntu distros)

---

• Add Melodic button to the wiki
• Add standard distribution wiki pages (planning, migration, etc...)
  • http://wiki.ros.org/melodic
  • http://wiki.ros.org/melodic/Planning
  • http://wiki.ros.org/melodic/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/melodic/Installation
    • Create main page http://wiki.ros.org/melodic/Installation
    • Create Platforms
    • Create DebianSources
    • Create DebEnvironment
    • Create PostInstall
    • All of the below should have a warning about distribution pending, like this: http://wiki.ros.org/action/diff/lunar/Installation/Ubuntu?action=diff&rev1=1&rev2=2
    • Create Ubuntu
    • Create Debian
    • Create Source

---

tag people once buildfarm is ready

• Release ros-core packages into Melodic
  • ros_environment
  • rosbag_migration_rule
  • roscpp_core
  • genmsg
  • gencpp
  • geneus Release into Melodic jsk-ros-pkg/geneus#57
  • genlisp Release into Melodic genlisp#13
  • gennodejs Release into Melodic RethinkRobotics-opensource/gennodejs#15
  • genpy
  • message_generation
  • message_runtime
  • ros_comm_msgs
  • std_msgs
  • cmake_modules Release into Melodic cmake_modules#47
  • rospack
  • ros
  • ros_comm
  • rosconsole_bridge
  • common_msgs common_msgs: 1.12.5-0 in 'melodic/distribution.yaml' [bloom] #16934
  • ros_tutorials
    • needs to be re-released as soon as the Melodic turtle is available
  • roslisp
• Release ros-base packages into Melodic
  • actionlib
  • angles
  • bond_core
  • dynamic_reconfigure
  • class_loader
  • pluginlib
  • nodelet_core
• common_tutorials

---

• Create melodic category on Discourse https://discourse.ros.org/c/release/melodic
• Announce availability of the Melodic build farm https://discourse.ros.org/t/melodic-morenia-buildfarm-available/4248
• Update mirror documentation (see https://github.com/ros-infrastructure/mirror/commits/master for examples)
• update ros mirrors (Melodic: Add artful and bionic to ROS mirror, artful to gazebo mirror. ros-infrastructure/mirror#14)
• update osrfoundation mirrors (wait until there are builds for ignition and gazebo for all supported platforms)
• Announce logo design and kick off t-shirt campaign

[dirk-thomas]

I have released all core package up to ros. That already unblocks several other packages.

The next one for me is ros_comm which will likely take quite a while before that will happen due to the significant amount of pending tickets.

[clalancette]

Excellent, thanks @dirk-thomas

[dirk-thomas]

I have released ros_comm and rosconsole_bridge. All my remaining packages are now blocked on pending other releases.

[mikaelarguedas]

@clalancette Initial release of ros_base packages has been done. Follow-up releases will come with potentially ABI/API breaking changes

[hrnr]

Hi all,

unfortunately Melodic was released with bug in generated doxygen documentation. The docs are missing top navigation bar, making them hard to navigate. See http://docs.ros.org/melodic/api/tf2_ros/html/c++/

The needed fix is ros-infrastructure/rosdoc_lite#82. The rosdoc_lite is not receiving much attention, so I'm posting here to let @clalancette know.

Could someone please merge the fix and regenerate all the doxygen docs on http://docs.ros.org?

Cheers,
Jiri

[tfoote]

@clalancette This looks to be hanging and the melodic launch is in the past. Can we close this out?

[clalancette]

Yeah, let's close this out.