[opencms-dev] Release Early, Release Often Re: how about schedule of OpenCms 8?

[Scintillance]

  Thanks to Michael for his explanation.

I guess the point is there is no such thing as 'working perfectly', else 
no-one would ever release software! I think the beta tag is enough to 
stop people from blindly using software which isn't ready for prime 
time; developers, on the other hand, can help to _make_ it ready, and 
often need to see what's coming over the horizon.

By choosing to hide OpenCms 8 in this way, Alkacon have unfortunately 
put off contributions, adoption etc by months. They've also made it more 
likely that current OpenCms users will jump ship and start using other 
CMSs. I have one customer who's doing exactly that; if they could see 
what was so fabulous about OpenCms 8, they might not.

While we're talking about the way software is shared, could we move to a 
modern VCS, e.g. Git :-)?

On 22/10/2010 19:57, Andreas Kuckartz wrote:
> There are arguments for not releasing source code during development
> which I would understand and not oppose but not this one.
>
> Here is why:
>
> Release Early, Release Often
> http://www.catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html
>
> Cheers,
> Andreas
> ---
>
> Michael Emmerich wrote:
>> When OpenCms 8 is released, it will be of course available in the public
>> CVS again.
>>
>> We always want to provide a working version in the CVS.
>> During development of a new version, this cannot be guaranteed,
>> therefore we will move the new version in the back in the CVS when
>> it is ready.