23 Jun
2005
23 Jun
'05
9:50 p.m.
There will be a release - in short time.
I decided that ;-)
However it's yet unclear when the best time is to make te branch
Derek Hinchliffe wrote:
jakov(a)vmlinux.org wrote:
Why not release every other month... it's not nonsensical.
It's agile.
If no big changes: 0.2.6.1
If big bugfixes: 0.2.7
If important features: 0.3
I think this is a very good idea.
Who am I? Well I guess I'm what you could call a typical reactos 'user' in
that I occaisionally download the latest releases to see how things are progressing.
Personally, I know that there is progress being made but only because I follow this list,
but I'm sure there are plenty of others who don't and just check the site for a
new release every now and then (or subscribe to the freshmeat release notices etc).
Now, I agree with other comments that if a new release (either 0.3 or 0.2.7) comes out
and there are no immediately visible improvements to the user then it could cause trust
issues. And on the other hand if there aren't any releases for a while then it looks
from the outside like the project is stagnating.
Which is why I think the above idea is a good one - if I've downloaded 0.2.6 in the
past and a 0.2.6.1 comes out 2 months later, then I know not to expect too many noticable
changes, but it indicates to me that there is at least progress behind the scenes. And
when the 0.2.7 comes out I should expect some new features around but nothing
breathtakingly new. And when 0.3 came out I'd be hitting the download ASAP to see what
major new developments are now afoot. So I think with the regular interval releases, but
making sure they are marked to indicate what sort of release they are, means everyone
knows where they stand.
Cheers
Derek
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev