Lunar Kick-Off Checklist

[mikaelarguedas]

This is a checklist of things to do for the Lunar kick-off (pre development and development):

• Choose distribution name: Lunar
• commission a logo
• Add to REP3 with proposed platforms and minimum requirements, request feedback from community Update REP3 for ROS Lunar Loggerhead ros-infrastructure/rep#123
• List on ROS wiki with expected release date (http://wiki.ros.org/Distributions)
• Add Ubuntu Z + Debian Stretch to bootstrap repository on repos.ros.org add zesty support ros-infrastructure/reprepro-updater#35
• Add Ubuntu Z + Debian Stretch to buildfarm_deployment_config add lunar targets ros-infrastructure/buildfarm_deployment_config#17 (note that one is not the live one it's for reference only)
• Add Ubuntu Z + Debian Stretch to ros_buildfarm/common.py added lunar targets ros-infrastructure/ros_buildfarm#360

---

• Add newly supported platforms to list of platforms for each Python package (in stdeb.cfg), in order of dependency (for ROS M, do this as soon as debs for new Ubuntu are available, in pre-alpha!):
  • rospkg (uploaded, no need to rerelease): ros-infrastructure/rospkg@60109b6
  • catkin_pkg (uploaded, no need to rerelease): ros-infrastructure/catkin_pkg@0b418ae
  • rosdistro (uploaded, no need to rerelease): ros-infrastructure/rosdistro@1ba7c97
  • rosdep (uploaded, no need to rerelease): ros-infrastructure/rosdep@4006765
  • vcstools (uploaded, no need to rerelease): vcstools/vcstools@a7b6e09
  • wstool (uploaded, no need to rerelease): vcstools/wstool@84f0fe6
  • rosinstall (uploaded, no need to rerelease): vcstools/rosinstall@5e12046
  • bloom (uploaded, no need to rerelease): ros-infrastructure/bloom@9e35e0f
  • rosinstall_generator (uploaded, no need to rerelease): ros-infrastructure/rosinstall_generator@c89c976
  • catkin_tools (uploaded, no need to rerelease): catkin/catkin_tools@e5bb5d8
  • vcstool: dirk-thomas/vcstool@25a7c54 and dirk-thomas/vcstool@953b294
• Use ros_release_python to make the currently released versions available in the new distros. Use the --include option
  - [ ] Import third-party packages for the newly targeted platforms Moved to Release checklist and ask maintainer to request the import of packages they need

---

• create Docker images for the new platforms for all targets Create a generic script for generating docker base images osrf/multiarch-docker-image-generation#1

---

• Create distribution files in ros/rosdistro Add lunar #13676
• add ros_buildfarm_config lunar entries Add lunar ros-infrastructure/ros_buildfarm_config#69
  • create new mailing list (https://groups.google.com/forum/#!forum/ros-buildfarm-lunar) with exactly the same settings as the existing ones
• generate new management jobs (see https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/deploy_configuration.rst)

---

• prerelease website
  • Add new column in for the new distro with theme and placeholder image Add lunar ros-infrastructure/prerelease_website#34 and Lunar fixups ros-infrastructure/prerelease_website#36
  • Add new LTS distros as preferred: add xenial to list of prefered distros ros-infrastructure/prerelease_website#35
  • Make xenial the preferred guest make xenial the recommended os ros-infrastructure/prerelease_website#37
  • Test prerelease process (except for latest ubuntu distros)

---

• Add Lunar button to the wiki
  - [ ] Add distribution to ROS browse tabs This should be on the Release checklist ( based on Lunar Kick-Off Checklist #13550 (comment))
  - [ ] Edit wiki pages to contain proper content for the Lunar tag. tracked by Lunar Check Wiki pages #13677 All these use the and_newer macros and thus will have proper content for lunar once generated
• Add standard distribution wiki pages (planning, migration, etc...)
  • http://wiki.ros.org/lunar
  • http://wiki.ros.org/lunar/Planning
  • http://wiki.ros.org/lunar/Migration
    • ros_comm http://wiki.ros.org/action/diff/lunar/Migration?action=diff&rev1=1&rev2=2
  • http://wiki.ros.org/lunar/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/lunar/Installation
    • Pages created http://wiki.ros.org/lunar/Installation
    • Fill out Ubuntu and Debian Installation pages

---

tag people once buildfarm is ready

• Release ros-base packages into Lunar
  • catkin (@dirk-thomas) ros-gbp/catkin-release@a62289f
  • genmsg (@dirk-thomas)
  • gencpp (@dirk-thomas)
  • geneus (@k-okada)
  • genlisp (@dirk-thomas)
  • genpy (@dirk-thomas)
  • gennodejs (@chris-smith @IanTheEngineer)
  • roscpp_core (@dirk-thomas)
  • message_generation (@dirk-thomas)
  • message_runtime (@dirk-thomas)
  • rosbag_migration_rule (@dirk-thomas)
  • std_msgs (@dirk-thomas)
  • ros_comm_msgs (@dirk-thomas)
  • cmake_modules (@wjwwood)
  • rospack (@dirk-thomas)
  • ros (@dirk-thomas)
  • roslisp (@dirk-thomas)
  • ros_comm (@dirk-thomas)
  • rosconsole_bridge (@dirk-thomas)
  • common_msgs (tfoote)
  • ros_tutorials (@dirk-thomas)
    • needs to be re-released as soon as the Lunar turtle is available
  • actionlib (mikaelarguedas)
  • angles (@tfoote)
  • bond_core (mikaelarguedas)
  • dynamic_reconfigure (mikaelarguedas)
  • class_loader (@mikaelarguedas)
  • pluginlib (mikaelarguedas)
  • nodelet_core (mikaelarguedas)
  • common_tutorials (wjwwood & stonier)

---

• Create lunar category on Discourse https://discourse.ros.org/c/release/lunar
• Announce availability of the Lunar build farm
• Update mirror documentation (see https://github.com/ros-infrastructure/mirror/commits/master for examples)
  • update ros mirrors add mirrors for lunar supported platforms ros-infrastructure/mirror#6
  • 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]

@k-okada Can you please release geneus into Lunar.

@chris-smith Can you please release gennodejs into Lunar.

It can be just the latest Kinetic release so that we can continue releasing the ROS core packages quickly. Thanks!

[chris-smith]

Done! ( through @IanTheEngineer )

[dirk-thomas]

@chris-smith @IanTheEngineer Thank you guys for the super quick action 🚀

[dirk-thomas]

@wjwwood Can you please release cmake_modules into Lunar including changes specific to Lunar (e.g. ros/cmake_modules#42).

[wjwwood]

Sure, here's the release pr: #13957

[dirk-thomas]

@wjwwood Thanks for the fast release.

[k-okada]

geneus done -> #13962

[dirk-thomas]

@k-okada Thank you for the quick release 🚀

[mikaelarguedas]

@tfoote you should be able to release common_msgs now that std_msgs and below have been released

[mikaelarguedas]

thanks @tfoote for the quick release!

[mikaelarguedas]

@stonier Can you please release common_tutorials into Lunar?

It can be just the latest Kinetic release. It's just to make sure that it actually builds properly.
Thanks!

[dirk-thomas]

Actually it won't build atm because of some parent sourcedeb jobs being stuck. Therefore it's also not possible to test it using Debian packages of the dependencies.

[stonier]

Aye, not going to build, but at least all the dependencies are there so it can be bloomed -> ros/rosdistro#13999.

When the deps are built, it should be right to go.

[dirk-thomas]

I added a new bullet to the second block in the first comment: third-party packages need to be imported into the repo for all newly targeted platforms. One example I ran into which is currently missing: ros-infrastructure/ros_bootstrap_dependencies#5

Looking at http://repositories.ros.org/status_page/lunar_default.html other packages seem to be missing as well.

[mikaelarguedas]

@dirk-thomas We decided to remove this bullet from this checklist and ask maintainers to request import of third party packages as they release. That allows us to flush out the packages that shouldn't be imported in the first place and to treat imports one at a time. So I'm going to remove this bullet and make it explicit on the release checklist ticket.

Thanks for pointing it out

[mikaelarguedas]

@ros/ros_team I'm not sure what the purpose of the Maintenance page is, so could use some input on the following proposal.

I am considering redirecting the Maintenance page to the status_page created for this purpose.

Pros:

• Up to date because generated periodically by the buildfarm
• Avoid having to generate manually the page every so often

Cons:

• It's not as eye friendly as the previous one and displays only the "Not released" packages

Alternative:

• generate a Maintenance page periodically during the beta cycle so that it stays roughly up to date
• leave it as is once all is green

Feedback welcome :)

[dirk-thomas]

I think the new status page should replace the former wiki page.

[tfoote]

+1 for replacing with the automated page. This wiki page was our manual approach to automating it.

I'd suggest replacing the contents with a little bit of tutorials on how to use the status pages effectively. (aka a few sentances explaining the search queries and terms.)

[wjwwood]

Yup, +1 for replacing it.

[mikaelarguedas]

sounds good, thanks all for the quick feedback, I'll do that then.

[mikaelarguedas]

@wjwwood can you confirm that "Add distribution to ROS browse tabs" was done in ros-infrastructure/rosbrowse#4 ?

Should this be a single item on the release checklist that consists in :

• adding the name of the next rosdistro (once ROS-M name has been decided)
• updating the active one
  and be completely removed from the Kickoff checklist?

[wjwwood]

That's the right pr to update rosbrowse. I agree it should be part of the release and not the kick-off checklist because we usually announce the next name at the release of the current one and we shouldn't update lunar to be the default until it is released.

[mikaelarguedas]

ok thanks for confirming, removing it from this checklist then

[wjwwood]

🎉