[Ros-release] Steps to cancel already-released packages
tfoote at osrfoundation.org
Mon Aug 12 07:23:17 UTC 2013
All you need to do is update the release.yaml file.
We've designed the system to be as stateless as possible. The buildfarm
will do a best effort build of what's in the release.yaml. It can handle
upgrades, rollbacks, additions and removals.
Conflicts with past and future packages are not a problem. It will
propagate through the various stages of the build pipeline only in a self
consistent state. So as long as the release.yaml doesn't have conflicts
the debs should not either.
Note this does not absolve you of considering your users and providing good
communication with respect to the development model. Your users should
know what's going on and depending on the development state of the package.
If there are expectations of stability for your users the buildfarm will
not prevent you from breaking compatibility.
PS I've copied this back to answers.ros.org and I've made the answer
slightly less specific. I believe your packages are very young so the
compatibility is not as much of an issue.
On Sun, Aug 11, 2013 at 5:29 PM, Isaac Isao Saito <130s at lateeye.net> wrote:
> Howdy ROS-Release,
> # someone suggests to ask a question like this here instead of answers .
> For a set of packages / a meta package that we already released into
> buildfarm (openrtm_common), we've figured out that we want to split it
> into multiple smaller sets / meta packages and fresh release each of
> them (for better modularity and moreover for easier handling of
> buildfarm error currently happening).
> What step should we take before releasing the new sets of packages?
> I'm afraid releasing new sets would cause conflicts if there already
> exist packages of the same names. Some packages have already been
> built and available on .deb binary repository. And just cancelling the
> commits for release.yaml on rosdistro  seems not sufficient either.
>  https://github.com/ros/rosdistro/blob/master/hydro/release.yaml
> Thank you,
> Ros-release mailing list
> Ros-release at code.ros.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-release