[Ros-release] Best practices for hosting bloom GBP release repositories?

William Woodall william at osrfoundation.org
Sat Mar 30 20:04:09 UTC 2013

On Sat, Mar 30, 2013 at 8:37 AM, Jack O'Quin <jack.oquin at gmail.com> wrote:

> I've finally managed to convert some packages to catkin and release
> them via bloom. The catkin conversions took far too long, but they
> seem to work, now. The bloom scripts work fine.
I'm sorry to hear that the catkinization took so long, I know you have been
asking questions related to catkinization on answers.ros.org, so hopefully
others who hit the same snags will find your Q/A's. Are there other
concrete things we can do to improve this for others?

> So far, I host my GBP release repositories in the same github
> organization that contains the corresponding source repo. I figure the
> same group of people do development, maintenance and releases. But, I
> suppose that's not necessarily true in general.
> As soon as its dependencies are available in Hydro, I will release a
> catkinized camera1394, which belongs to the ros-drivers organization.
> I don't see any other GBP repos in ros-drivers. Many ROS core packages
> are released via the ros-gbp organization.
>  * What are the advantages of that approach?

I think the reason we have done that historically, was because the
organizations were already large, and having the release repositories in
the sam organization would double the size, really cluttering things up.

The side affect of this is that as a person who is keeping the build farm
running, I don't have to know which organization a given repository is, I
can guess at the url: github.com/ros-gbp/<repo>-release. If that doesn't
hit, then I have to go to the rosdistro file and look up the location of
the release repository.

>  * What is the recommended hosting scheme for packages like mine?

If you are releasing code into one of the ros-* organizations then you
should probably put the release repository in ros-gbp, if you need
permission just ask. Otherwise host the release repository in the same org
as the upstream source or create your own -gbp org if things are getting

> --
>  joq
> _______________________________________________
> Ros-release mailing list
> Ros-release at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-release
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20130330/fc38a6dd/attachment-0009.html>

More information about the Ros-release mailing list