code.ros.org is currently unmaintained, and the license key for it has
expired, so it's difficult to add new users, grant new permissions or
do other maintenance. Code checkouts still work, so it's still
possible to migrate existing code off of code.ros.org.

My understanding is that most of the packages on code.ros.org have
been migrated to github.

For the PR2 packages, I've migrated as many packages as I can, but
it's been a rush, and while everything I've released into Hydro has
been released from github, I've only had time to update the repository
information for older packages when I release them into an older
distro. I suspect most other maintainers are in a similar situation.

-Austin

On Tue, Oct 1, 2013 at 8:59 AM, Jack O'Quin <jack.oquin@gmail.com> wrote:
> Looking through ros/rosdistro, I see lots of doc references for Electric and
> Fuerte, with 31 doc references in Groovy, and none for Hydro.
>
> Why are there no Hydro references? Are they all old, wet packages that will
> never be released in Hydro?
>
> Are those repositories still supported? I see no point in breaking so many
> documentation links while those distros remain in common use.
>
> Aren't people being encouraged to move new development of their packages
> elsewhere, like github?
> --
>  joq
>
> _______________________________________________
> ros-release mailing list
> ros-release@lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>