Preparing for Kinetic Sync 2020-06-10

[tfoote]

Kinetic Maintainers,

We’re due for another Kinetic sync. We have 39 packages ready for sync. And I’ve identified one regression of a metapackage due to including a new package that’s failing to build. It’s ticketed here:

rr_rover_zero_driver missing rospy dependency

If there’s anything else that should be tracked please reply here. Otherwise I plan to hold new release until Friday.

[Achllle]

What does a Sync freeze exception mean?

[tfoote]

We’re freezing for a sync. As the release manager I made a judgement call to allow that package to be released into this sync, thus an exception from the sync release freeze.

Note that it’s failed to build as there appears to be a missign dependency, but since it’s a new package it doesn’t cause a regression.

[tfoote]

The sync is out:

New Packages for Kinetic 2020-06-12

We’re happy to announce 2 new packages and 35 updated packages. There’s one regression of a metapackage due to a new dependency that failed to build. Thank you to all the contributors and maintainers who helped make these packages available! Package Updates for kinetic Added Packages [2]: ros-kinetic-phidgets-msgs: 0.7.10-1 ros-kinetic-rr-openrover-simulation: 1.0.0-3 Updated Packages [35]: ros-kinetic-audio-capture: 0.3.5-1 -> 0.3.6-1 ros-kinetic-audio-common: 0.3.5-1 -> 0.3.6-1 ros-kin…

[Achllle]

I made a judgement call to allow that package to be released into this sync, thus an exception from the sync release freeze.

I’m a bit confused on the wording here, since the package was not released, you mean to say that the package was not allowed to be released? (by the way, the build fails were fixed)

[tfoote]

You as the upstream developer make a release of the upstream package. Which results in a tag on the upstream repository 0.3.1

But your pull request releases the packge into the kinetic rosdistro. This is the release that most people care about and track. When we’re preparing for a sync we have a quiet period where we prevent releases into the rosdistro to make sure that we can run tests and be confident that things have built fully. In this case by default I held any new releases starting Wednesday until I ran the sync today on Friday.

@Achllle

(by the way, the build fails were fixed)

I see that you’ve fixed your master branch and the devel job is passing, but until you release your source code with a new version and rerun bloom to create a new release into kinetic the build failures will not be fixed for anyone using kinetic unless the explicitly ask for the upstream devel branch from source which is unusual and not generally recommended as that’s unreleased code and not guaranteed to be compatible if the maintainer is doing a coordinated release or refactoring is in process.

[Achllle]

Thank you for the explanation, that helps clear things up