<div dir="ltr">Then ... my next question would be:<div><br></div><div> Why isn't there more resistance w.r.t. switching to master ?</div><div><br></div><div>I mean, when you say "oh I had a bug on syskit on next", did you report it as a functionality bug on next ? Did you insist that it should be fixed *on next* ? instead of switching to master ?</div>
<div><br></div><div>For new functionality, how much of it is "oh but I need X, it is so shiny" instead of "without X, I really cannot do it !". I mean, when I worked on the Orion I *wanted* some features from master, but quickly realized that I did not *need* them. I had what was strictly needed to get the Joints type (meaning typelib/master but orogen/next)</div>
<div><br></div><div>As for the release schedule / frequency, I can only do +1. Releases are too far apart.</div><div><br></div><div>My big problem here is that master has become the de-facto version of Rock that everyone uses, which really hinders possibility to do some actual development.</div>
<div><br></div><div>Sylvain</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 4, 2014 at 3:54 PM, Matthias Goldhoorn <span dir="ltr"><<a href="mailto:matthias.goldhoorn@dfki.de" target="_blank">matthias.goldhoorn@dfki.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
<div>On 04.06.2014 15:43, Sylvain Joyeux
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Is that everyone seem to think that they need
master. The majority should be using stable or next.
<div><br>
</div>
<div>Now, I *know* that there are reasons (there are always
reasons) why one might think that master is required. However,
the main question for me is:</div>
<div><br>
</div>
<div> How can we make people feel confident that they can use
next ?</div>
<div><br>
</div>
<div>Or</div>
<div><br>
</div>
<div> How can we ensure that 'next' can be used except for a
few packages that would go on master ?</div>
<div><br>
</div>
<div>The best way to start answering these questions is to
answer another one:</div>
<div><br>
</div>
<div> Why are you on master ?</div>
</div>
</blockquote>
<br></div></div>
Because i using syskit and the next version is even more unstable
than master. I had several times that the depandancy between
roby/syskit and other 'core' packages is hard. So i cannot stay a
long time on next and only with syskit/roby on master.<br>
Indeed i'm not sure if i can currently use syskit/roby on next and
everything else on master.<br>
<br>
So generally speaking, incompatibilities between
syskit/roby/utilmm/utilrb/typelib/orogen/ base/types/(std)<br>
<br>
<br>
The Second point, is that the release cycle to next is to long for
new features, i i (as rock-dev) add new features to rock. I take
ofter months before it goes into next.<br>
Therefore i have (due to the same reasons above) switch to master,
also for other members of my project. I would prefer a shorter
release time between master/stable/next...<br>
<br>
<br>
<br>
Best,<br>
Matthias<div class=""><br>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Sylvain </div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Rock-dev mailing list
<a href="mailto:Rock-dev@dfki.de" target="_blank">Rock-dev@dfki.de</a>
<a href="http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev" target="_blank">http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev</a>
</pre>
</blockquote>
<br>
<br>
</div><pre cols="72">--
--
Matthias Goldhoorn
Unterwasserrobotik
Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany
Phone: <a href="tel:%2B49%20%280%29421%20218-64100" value="+4942121864100" target="_blank">+49 (0)421 218-64100</a>
Fax: <a href="tel:%2B49%20%280%29421%20218-64150" value="+4942121864150" target="_blank">+49 (0)421 218-64150</a>
E-Mail: <a href="mailto:robotik@dfki.de" target="_blank">robotik@dfki.de</a>
Weitere Informationen: <a href="http://www.dfki.de/robotik" target="_blank">http://www.dfki.de/robotik</a>
-----------------------------------------------------------------------
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
-----------------------------------------------------------------------
</pre>
</div>
</blockquote></div><br></div>