[Rock-dev] Release candidate of rock.core

[Sylvain Joyeux]

I've had a look. The problem is that so far we were releasing
rock.core with rock. This is not the model anymore - and rock.core
removed the backward headers that have been sitting for years in
base/types.

In principle, "one" should have had intermediate releases of the
non-core packages which would have dealt with the migration issues.
However, this has never been a model we pushed developers for.

A few options forward:
- re-add the backward headers to this release, and figure out the
update model going forward.
- create a rock-15.05-core with only the core pinned. This would allow
people that are still using rock 15.05 to upgrade their systems
step-by-step.
- just leave as it is and let people deal with the resulting mess.

Sylvain

On Wed, Jul 19, 2017 at 7:59 AM, Raul Dominguez <Raul.Dominguez at dfki.de> wrote:
> Hi,
>
> Although your email is not asking for feedback. I hope this is the right
> channel to provide it.
>
> I tested the release candidate today with a simple network: Dynamixel,
> Hokuyo and Tilt_scann task. The "stable" branches of those repositories
> (default option) don't build I had to override to master. It then
> updated and built correctly. I haven't run the tasks though.
>
> I used autoproj 2.1. rc.
>
> I will test it soon on the robot.
>
>
> Kind regards,
>
> Raúl
>
>
>
> On 05.06.2017 21:53, Sylvain Joyeux wrote:
>> The rock-rc branch of https://github.com/rock-core/buildconf now
>> builds what should become the next rock.core release (as in: builds
>> fine in a 16.04 system from scratch, and tests that were passing still
>> pass). As usual, it needs testing.
>>
>> To bootstrap from scratch:
>>
>>     ruby autoproj_bootstrap git https://github.com/rock-core/buildconf
>> branch=rock-rc
>>
>> To apply on an existing install, assuming that you have an up-to-date
>> base/scripts (from today):
>>
>>     rock-release versions refs/heads/rock-rc >
>> autoproj/overrides.d/99-rock-rc.yml
>>
>> After adding the version file, the safest thing to do is to check
>> what's different with
>>
>>     autoproj status
>>
>> (Note: the refs/heads/ is necessary because there was a rock-rc tag in
>> the buildconf repository. I just deleted the tag, but deletion of tags
>> is not propagated ... A.k.a. don't create tags for things that are
>> meant to be temporary)
>>
>> Sylvain
>> _______________________________________________
>> Rock-dev mailing list
>> Rock-dev at dfki.de
>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
>
> --
>   Raúl Domínguez (M.Sc.)
>   Space Robotics
>
>   Besuchsadresse der Nebengeschäftsstelle:
>   DFKI GmbH
>   Robotics Innovation Center
>   Robert-Hooke-Straße 5
>   28359 Bremen, Germany
>
>   Postadresse der Hauptgeschäftsstelle Standort Bremen:
>   DFKI GmbH
>   Robotics Innovation Center
>   Robert-Hooke-Straße 1
>   28359 Bremen, Germany
>
>   Tel.:     +49 421 178 45-6617
>   Zentrale: +49 421 178 45-0
>   Fax:      +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
>   E-Mail:   raul.dominguez at dfki.de
>
>   Weitere Informationen: http://www.dfki.de/robotik
>   -----------------------------------------------------------------------
>   Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
>   Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
>   Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
>   (Vorsitzender) Dr. Walter Olthoff
>   Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
>   Amtsgericht Kaiserslautern, HRB 2313
>   Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
>   USt-Id.Nr.:    DE 148646973
>   Steuernummer:  19/673/0060/3
>
> _______________________________________________
> Rock-dev mailing list
> Rock-dev at dfki.de
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev