[ros-users] Roll out of new rosdistro today - expect service interruptions

[Edwards, Shaun M.]

Dirk,

That's my problem, the packages are still on the old build system.  My bad.

Shaun Edwards
Senior Research Engineer
Manufacturing System Department


http://robotics.swri.org
http://rosindustrial.swri.org/
http://ros.swri.org
Join the ROS-Industrial Developers List
Southwest Research Institute
210-522-3277


-----Original Message-----
From: ros-users-bounces at code.ros.org [mailto:ros-users-bounces at code.ros.org] On Behalf Of Dirk Thomas
Sent: Tuesday, April 23, 2013 10:50 PM
To: User discussions
Subject: Re: [ros-users] Roll out of new rosdistro today - expect service interruptions

Hi Shaun,

all information from the ros/rosdistro repository for Groovy and Hydro has been converted to the new format.

The state before the conversion is available on a branch: https://github.com/ros/rosdistro/blob/before-rep137/releases/groovy.yaml
I can't find industrial_core in there and that is also the reason why it does not appear in the new file groovy/release.yaml.

Is your package actually wet?
If not, all dry stuff has not changed in is still maintained in the old rosdistro file in the SVN repository on code.ros.org.
Dry stuff is not effected by REP 137 at all since it e.g. not even has gbp repositories etc.

- Dirk


On 23.04.2013 20:42, Edwards, Shaun M. wrote:
> Dirk,
>
> Should we expect to see existing releases in release.yaml file.  For example industrial_core is released for groovy but I cannot find it in groovy/release.yaml?
>
> Shaun Edwards
> Senior Research Engineer
> Manufacturing System Department
>
>
> http://robotics.swri.org
> http://rosindustrial.swri.org/
> http://ros.swri.org
> Join the ROS-Industrial Developers List Southwest Research Institute
> 210-522-3277
>
> -----Original Message-----
> From: ros-users-bounces at code.ros.org 
> [mailto:ros-users-bounces at code.ros.org] On Behalf Of Dirk Thomas
> Sent: Monday, April 22, 2013 9:58 PM
> To: User discussions
> Subject: Re: [ros-users] Roll out of new rosdistro today - expect 
> service interruptions
>
> The roll out of the new rosdistro format is completed.
>
> Please make sure to update to the latest packages since older versions of these tools will not continue to work.
>     (E.g. run "sudo apt-get update && sudo apt-get dist-upgrade")
>
>     * python-rosdep 0.10.18
>     * python-rosdistro 0.2.2
>     * python-vcstools 0.6.27
>
> For releasing packages you will find the files for Groovy and Hydro in a slightly different location:
>     https://github.com/ros/rosdistro/blob/master/groovy/release.yaml
>     https://github.com/ros/rosdistro/blob/master/hydro/release.yaml
> If you send pull requests for rosdistro please ensure that they are based against the current master.
> The next update to bloom will reenable the automatic pull request generation.
>
> To register repositories for devel jobs the sibling files with the name "source.yaml" are used.
>     https://github.com/ros/rosdistro/blob/master/groovy/source.yaml
>     https://github.com/ros/rosdistro/blob/master/hydro/source.yaml
>
> The information to document repositories is now stored in a single file doc.yaml in the subfolder named after the ros distribution.
>     https://github.com/ros/rosdistro/blob/master/groovy/doc.yaml
>     https://github.com/ros/rosdistro/blob/master/hydro/doc.yaml
> The doc how to register repositories with dependencies has been updated (http://www.ros.org/wiki/Get%20Involved).
>
> If you see any issues which might relate to the todays updates please let me know - either via the mailing list or a specific issue tracker.
>
> - Dirk
>
>
>
> On 22.04.2013 09:15, Dirk Thomas wrote:
>> Today I will start rolling out the new rosdistro files and implementation (REP 137).
>> This will include the following actions:
>>
>> * freeze current state of rosdistro files https://github.com/ros/rosdistro
>>     * please do not send further pull requests since they can not be 
>> applied to the new format anyway
>> * stop running the build farm, prerelease and rosinstall generator 
>> website
>> * verify that the generated new rosdistro files are consistent and 
>> complete
>> * replace the old rosdistro files with the new ones
>> * release all affected tools (buildfarm, jenkins_scripts, 
>> jenkins_tools, prerelease_website, rosinstall_gen, rosdep, roslocate)
>> * deploy them to the servers
>> * restart and check all services one-by-one
>>
>> During the roll out period I am doing my best to keep disruption of services short.
>>
>> After the roll out I will send another email with updates.
>> Users can expect to update at least rosdep and vcstools (since it should be the only tools they are affected by).
>>
>> Sorry for any inconvenience this causes.
>
>
> --
>
> Dirk Thomas
> ROS Development Team
> dthomas at osrfoundation.org
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>

_______________________________________________
ros-users mailing list
ros-users at code.ros.org
https://code.ros.org/mailman/listinfo/ros-users