[ros-dev] Discussion: Release policy changes
stapostol at gmail.com
stapostol at gmail.com
Sat Dec 9 16:25:24 CET 2006
Την Sat, 09 Dec 2006 17:13:24 +0200,ο(η) Ged Murphy <gedmurphy at gmail.com>
έγραψε:
> On 12/9/06, Aleksey Bragin <aleksey at studiocerebral.com> wrote:
>>
>> Hello,
>> I'd like to hear opinions regarding the change in release policy.
>>
>> The proposition:
>> Release happens on a strict time basis, like once per month. That
>> means, at the end of the month we look for the best revision inside
>> this month (probably which is closer to the end of the month), branch
>> from it, apply all fixes (if any), and release.
>>
>> Disadvantage: a few coming releases' quality will be overall lower,
>> there might be things like 0.3.25 (if release frequency is set too
>> high, and this is not a disadvantage actually).
>>
>> Advantages: in the long run quality goes up, more developers due to
>> higher release rate, more publicity, people will finally realize it's
>> an alpha product, more bugs reported, no signs of a dead project (I
>> doubt there are healthy projects doing 1 release per year :)).
>>
>> Any thoughts are appreciated.
>
This is exactly what is needed to get more developers interested in the
project, plus, increased publicity equals more testing which can only be a
good thing.
- Stephen A
More information about the Ros-dev
mailing list