<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Thomas started a page on this :<br>
<a class="moz-txt-link-freetext" href="https://rock.opendfki.de/wiki/WikiStart/OngoingWork/RockFlavorsOrReleases">https://rock.opendfki.de/wiki/WikiStart/OngoingWork/RockFlavorsOrReleases</a><br>
      <br>
      Feel free to add some bullet points<br>
      Greetings<br>
      &nbsp;&nbsp;&nbsp; Janosch<br>
      <br>
      On 10.07.2014 14:07, Sylvain Joyeux wrote:<br>
    </div>
    <blockquote
cite="mid:CAKDpF4T4MW4yfVUhzrsut8OC+67G6352EvnvRdWoGHVPUrwGAA@mail.gmail.com"
      type="cite">
      <div dir="ltr">Before we have an idea for a transition plan, I
        would argue that we should have an implementation plan... As you
        mention, autoproj commit / autoproj tag have to be implemented
        prior to the release management changes.
        <div>
          <br>
        </div>
        <div>Here comes the neverending question: who has the time ?<br>
          <div><br>
          </div>
          <div>Sylvain</div>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, Jul 10, 2014 at 10:00 AM, Jakob
          Schwendner <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:jakob.schwendner@dfki.de" target="_blank">jakob.schwendner@dfki.de</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
            <br>
            Any ideas on a transition plan for these changes? I guess
            the autoproj commit feature could be independent from having
            releases instead of our master/next/stable cycle.<br>
            <br>
            Cheers,<br>
            <br>
            Jakob<br>
            <div class="HOEnZb">
              <div class="h5"><br>
                &gt; -----Original Message-----<br>
                &gt; From: <a moz-do-not-send="true"
                  href="mailto:rock-dev-bounces@dfki.de">rock-dev-bounces@dfki.de</a>
                [mailto:<a moz-do-not-send="true"
                  href="mailto:rock-dev-bounces@dfki.de">rock-dev-bounces@dfki.de</a>]
                On<br>
                &gt; Behalf Of Sylvain Joyeux<br>
                &gt; Sent: Dienstag, 1. Juli 2014 11:21<br>
                &gt; To: Steffen Planthaber<br>
                &gt; Cc: <a moz-do-not-send="true"
                  href="mailto:rock-dev@dfki.de">rock-dev@dfki.de</a><br>
                &gt; Subject: Re: [Rock-dev] Flavours, freezes, updates<br>
                &gt;<br>
                &gt; Thanks Steffen, your summary is IMO quite accurate.<br>
                &gt;<br>
                &gt;<br>
                &gt; &nbsp; &nbsp; &nbsp; Using the tags you can easily find and
                reproduce former states of the<br>
                &gt; &nbsp; &nbsp; &nbsp; software. This is only true for a complete
                snapshot of all packages, so<br>
                &gt; &nbsp; &nbsp; &nbsp; it it only useful directly after a autoproj
                commit. Both can be<br>
                &gt; combined<br>
                &gt; &nbsp; &nbsp; &nbsp; into a single command<br>
                &gt;<br>
                &gt;<br>
                &gt; They can, but they should not IMO. The same way
                than git commit and git tag<br>
                &gt; are two different things, I would keep autoproj
                commit and autoproj tag<br>
                &gt; separate. If only to reuse prior knowledge about
                git.<br>
                &gt;<br>
                &gt; Sylvain<br>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Rock-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rock-dev@dfki.de">Rock-dev@dfki.de</a>
<a class="moz-txt-link-freetext" href="http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev">http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
 Dipl. Inf. Janosch Machowinski
 SAR- &amp; Sicherheitsrobotik

 Universit&auml;t Bremen
 FB 3 - Mathematik und Informatik
 AG Robotik
 Robert-Hooke-Stra&szlig;e 1
 28359 Bremen, Germany
 
 Zentrale: +49 421 178 45-6611
 
 Besuchsadresse der Nebengesch&auml;ftstelle: 
 Robert-Hooke-Stra&szlig;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:  <a class="moz-txt-link-abbreviated" href="mailto:jmachowinski@informatik.uni-bremen.de">jmachowinski@informatik.uni-bremen.de</a>

 Weitere Informationen: <a class="moz-txt-link-freetext" href="http://www.informatik.uni-bremen.de/robotik">http://www.informatik.uni-bremen.de/robotik</a>
</pre>
  </body>
</html>