[Ros-release] Release updates for electric (in general old ROS releases)
Florian.Weisshardt at ipa.fraunhofer.de
Thu Jul 12 09:22:04 UTC 2012
as I mentioned before we still depend on electric, so please let me know how we can support you to get the electric updates public.
Von: Vincent Rabaud [mailto:vrabaud at willowgarage.com]
Gesendet: Dienstag, 10. Juli 2012 18:19
An: Weißhardt, Florian
Cc: ros-release at code.ros.org
Betreff: Re: [Ros-release] Release updates for electric (in general old ROS releases)
Hi Florian, there is no regular schedule as that depends on whether there are any build jobs running. The Electric synchronization was indeed neglected as we focused more on Fuerte. We'd be very happy to have people help us with that so please contact us if you want to help.
Anybody can subscribed to the shadow repository (the repository before the synchronization to the official one), its address is:
(it is useful to track regressions before we things are made public)
Synchronization is just a matter of running a script but it has to be done manually to make sure the state of the release is stable: stable meaning the http://www.ros.org/debbuild/electric.html page "looks" stable.
Releases are now supported for a year (so only Electric and Fuerte are supported at the moment).
On Tue, Jul 10, 2012 at 4:43 AM, Weißhardt, Florian <Florian.Weisshardt at ipa.fraunhofer.de> wrote:
I wonder if there is a (regular) shedule for updating the pending electric or in general old ROS releases? The current state of the public electric repository is still 15th of June, which is over 4 weeks ago now. As many of us are still working on electric it would be good to be able to estimate when a new releases will be available on the public repository. E.g. more or less strict release cyle of one, two or 4 weeks for the previous ROS distribution? Maybe longer for older ROS distributions? Is there some rule which defines an End-Of-Life cycle for a ROS distribution?
Is there much manual work to do to shift the shadow-fixed repository into public? Is there something which can be done to accelerate or facilitate this process?
Ros-release mailing list
Ros-release at code.ros.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-release