Revision history [back]

There has been an announcement on the ros-release mailing list. I can't point to the archive since that is not yet available after the migeation to the OSUOSL.

<<<

We are continuing our migration of ROS services. Today the release repository for dry packages has been moved from code.ros.org to Google code (https://code.google.com/p/ros-dry-releases/).

The new repository location requires every maintainer who wants to release dry packages in the future to re-do the setup instructions (http://www.ros.org/wiki/release/Setup/Machine):

• update the installed Debian package "python-rosrelease" to version >= 0.2.11

• get a fresh checkout of the release tools from their new location

• request to join the ros-dry-releases project by sending an email to ros-release@code.ros.org with your Googlecode login

>

If you are releasing ROS packages you might want to sign up for that mailing list since important release information is posted there.

There has been an announcement on the ros-release mailing list. I can't point to the archive since that is not yet available after the migeation to the OSUOSL.

<<<{{{

We are continuing our migration of ROS services. Today the release repository for dry packages has been moved from code.ros.org to Google code (https://code.google.com/p/ros-dry-releases/).

The new repository location requires every maintainer who wants to release dry packages in the future to re-do the setup instructions (http://www.ros.org/wiki/release/Setup/Machine):

• update the installed Debian package "python-rosrelease" to version >= 0.2.11

• get a fresh checkout of the release tools from their new location

• request to join the ros-dry-releases project by sending an email to ros-release@code.ros.org with your Googlecode login

If you are releasing ROS packages you might want to sign up for that mailing list since important release information is posted there.

There has been an announcement on the ros-release mailing list. I can't point to the archive since that is not yet available after the migeation to the OSUOSL.

We are continuing our migration of ROS services.  Today the release repository for dry packages has been moved from code.ros.org to Google code (https://code.google.com/p/ros-dry-releases/).
(https://code.google.com/p/ros-dry-releases/).
  
The new repository location requires every maintainer who wants to release dry packages in the future to re-do the setup instructions (http://www.ros.org/wiki/release/Setup/Machine):(http://www.ros.org/wiki/release/Setup/Machine):
  
 
* update the installed Debian package "python-rosrelease" to version >= 0.2.11
0.2.11
 
* get a fresh checkout of the release tools from their new locationlocation
 
* request to join the ros-dry-releases project by sending an email to ros-release@code.ros.org with your Googlecode login
 
 
}}}login

There has been an announcement on the ros-release mailing list. I can't point to the archive since that is not yet available after the migeation to the OSUOSL.

We are continuing our migration of ROS services.  Today the release repository for dry packages has been moved from code.ros.org to Google code (https://code.google.com/p/ros-dry-releases/).

The new repository location requires every maintainer who wants to release dry packages in the future to re-do the setup instructions (http://www.ros.org/wiki/release/Setup/Machine):

* update the installed Debian package "python-rosrelease" to version >= 0.2.11

* get a fresh checkout of the release tools from their new location

* request to join the ros-dry-releases project by sending an email to ros-release@code.ros.org with your Googlecode login

If you are releasing ROS packages you might want to sign up for that mailing list since important release information like this is posted there.