[Ros-release] Steps to cancel already-released packages

[Isaac Isao Saito]

Tully,

thanks for the explanation, and also for the one-stop service; that
sounds super nice and easy to use!

And yes the packages are indeed very young (in ROS ecosystem) and we
haven't advertised to anybody so that no one hopefully has started
using, and thus we don't expect any no confusion from users yet. But
we'll keep in mind your advice upon cancelling any released pkgs in
the future (although we'll try to optimize the design the best so that
we won't have to cancel again).

Isaac


On Mon, Aug 12, 2013 at 2:23 AM, Tully Foote <tfoote at osrfoundation.org> wrote:
> 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.
>
> Tully
>
>
> 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
>> [0].
>>
>> 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 [1] seems not sufficient either.
>>
>> [0]
>> http://answers.ros.org/question/72103/steps-to-cancel-already-released-packages/?comment=72139#comment-72139
>> [1] https://github.com/ros/rosdistro/blob/master/hydro/release.yaml
>>
>> Thank you,
>>
>> Isaac
>> _______________________________________________
>> Ros-release mailing list
>> Ros-release at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-release
>
>