[ros-dev] Discussion: Release policy changes

[Klemens Friedl]

2006/12/9, Aleksey Bragin <aleksey at studiocerebral.com>:
> 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.

I like the idea.

> 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 :)).


 A release once per months, is exactly what we need. It means more
stable versions for normal tester / community member. So, there will
be no need for them to try out trunk-builds and ask questions ala
"bootcd don't build", "compile errors", etc.
We can submit more news events to media, which will hopefully result
in more new developers and more publicity in general.

As soon as the automatic regression testing system is active, plus
more up-to-date third party libs and some kernel fixes, ReactOS will
be a lot more stable than ever before and additionally more compatible
with WinNT 4/5x/6.

OpenOffice 1.x, AbiWord 2.x, OpenGL, SDL, ... we will then be useable
again, plus a lot more applications like Photoshop 3-7, etc.


Best regards,
Klemens Friedl