On 28/07/15 09:48, Chris Johns wrote:
>>>>
>>>>Either scheme fits pretty well with RTEMS release cycle I think. Even
>>>>if we can get down to one release per year, the numbers won't grow
>>>>terribly fast.
>>>
>>>One release per year would be nice.
>>>
>>
>>We may need more flexibility.
>
>I just wanted to say, that the four years or so it took to release RTEMS 4.11 
was a bit long.
>
Yes I agree. I think Joel wants a 4.12 which is close to 4.11 but
stripped of various things we kept in 4.11.

Once we have 5.0 and waf, buildbot will decide when a release is ready.
When the feature set for the release is available and buildbot shows the
code is suitable it can be released. It might be months or just weeks.

We have the 4.11 release branch, but still no release. Independent of that, we have to adjust the version of the master. Will this be 4.12.99 or 5.0.0?

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to