I agree, though I'd go for more releases with fewer features each
time, personally. Less "work in progress" and way more customer
satisfaction. Also, it's way easier to wait 1-2, or even 2-4 months
than 3-4 months, if sometimes it's 2. Having said that OpenBSD
releases twice a year like clockwork and the regularity of their
release really works. Meh. Hopefully soon. :)
Christian.
On May 5, 2010, at 3:21 AM, Massimo Lusetti wrote:
On Wed, May 5, 2010 at 8:21 AM, Igor Drobiazko <[email protected]
> wrote:
I'm looking forward to see the new stuff but sometimes we have to
deliver
less than we would like to deliver. Waiting for a release 12-18
month is
unacceptable for any client. I guess, same applies for open source.
Ideally
there are 2-3 smaller releases per year. We put in every release as
much as
we can. If some innovative and cool stuff isn't ready to be
released, we
move it. It's no problem, because the next release is in 3-4 months.
Plain right. And I remember a vote or a discussion where a release
cycle ala-Tomcat was chosen where the project release quite often and
then a vote will be casted on a specific release number to declare it
the "stable" one.
I believe that the release strategy is one of the factor to success.
Again completely agree.
Cheers
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
