Well ... Then we could at least make parallel releases, one "new style" for the not-so-faint-of-heart-who-need-it-right-now (i.e. spacebot, sauce) and one "old style" for those that don't want to have to resolve the issues that will arise. I.e., let's not push a new release strategy on all new users just because DFKI has two upcoming competitions.
Changing how the installation & update process behaves is not a small thing. I would prefer giving the option to keep to the old system as long as the new one is not "tested". Sylvain On Fri, Aug 8, 2014 at 4:17 PM, Janosch Machowinski <[email protected]> wrote: > As far as I understood it, the "autoproj commit" stuff > aims at freezing everything, that is not handled by the > normal release, and is an addition to the release process. > > Anyway, at some point we need to test the release process > and as we got SAUCE-E and Spacebot upcoming, now > would be a good time, to create a release. If the process itself > turn out to be suboptimal we can still decide to change it the > next time. But we won't know that, until we tried it out... > Greetings > Janosch > > Am 08.08.2014 19:29, schrieb Sylvain Joyeux: >> Dumb question ... But why rushing using the "new" release mode BEFORE >> we have it nailed instead of doing one more release with the current >> release method and switch to the new one next time ? >> >> I mean, with the "autoproj commit" stuff from jakob, we have quite a >> bit of things to think about and solve before switching to a new >> release model... And I would rather not change 5 times how things work >> release-wise. >> >> Sylvain >> >> On Fri, Aug 8, 2014 at 11:15 AM, Janosch Machowinski >> <[email protected]> wrote: >>> Hey, >>> as we all agreed, we want to do a release. In the DFKI, we agreed, that >>> NOW would be a good moment. As a result of Sylvains concerns, we >>> modified the release process. >>> >>> On Wednsday the 13.8.14 we will branch all Packets, known to Rock-Next >>> from the Master branch to Rock201408_rc1. >>> EXCEPT you mail me and tell me not to use Master but commit XXX for >>> your packet. (The idea is to have at least work on everyone as possible) >>> >>> For all packets, which are only on Master at the moment, we need to decide >>> how to go on with them. Best would be if packet maintainers give me a >>> Go or NoGo for these packages. >>> >>> This should be all until Wednesday. >>> Greetings >>> Janosch >>> >>> >>> >>> >>> -- >>> Dipl. Inf. Janosch Machowinski >>> SAR- & Sicherheitsrobotik >>> >>> Universität Bremen >>> FB 3 - Mathematik und Informatik >>> AG Robotik >>> Robert-Hooke-Straße 1 >>> 28359 Bremen, Germany >>> >>> Zentrale: +49 421 178 45-6611 >>> >>> Besuchsadresse der Nebengeschäftstelle: >>> Robert-Hooke-Straße 5 >>> 28359 Bremen, Germany >>> >>> Tel.: +49 421 178 45-6614 >>> Empfang: +49 421 178 45-6600 >>> Fax: +49 421 178 45-4150 >>> E-Mail: [email protected] >>> >>> Weitere Informationen: http://www.informatik.uni-bremen.de/robotik >>> >>> _______________________________________________ >>> Rock-dev mailing list >>> [email protected] >>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev >> _______________________________________________ >> Rock-dev mailing list >> [email protected] >> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev > > _______________________________________________ > Rock-dev mailing list > [email protected] > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
