On Mon, Aug 18, 2014 at 11:39 AM, Janosch Machowinski <[email protected]> wrote: > Hm, ok. Then a question (for I guess Matthias and Thomas), if this code > is so pre alpha, > why in gods name are we using it to run our systems in a competition ? Because that's their call to make. From my p.o.v.: you don't care about the toolchain, fair enough. They do, and a competition is actually a good place to harden software *if* you are ready to spend the time needed to stabilize it.
The bottom line is: if you get that on stable, you basically decide *for me* that I should spend the time to stabilize it. You don't have the right to do that. I can only repeat what I said: the only person that can decide if some piece of code should go on stable *is the person maintaining it*. You can't decide for him whether (1) it is of sufficient quality and (2) that person can spend the time necessary to fix bugs quickly (something we all expect on a stable release). >> +1 on Matthias' comment: a release is not meant to stabilize alpha-quality >> code. > Just in general : We are still in the RC phase. For me this is a phase, > were code can still be > integrated, or dropped. Of unstable code ? The RC phases should be short (or you are just creating a new 'next'), which does not allow for stabilizing unstable code. Sylvain _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
