I agree.
On Thu, 1 Feb 2001, danch wrote:
> This prompts me to ask a general question.
>
> Are there any plans post 2.1 to separate a development branch of jBoss
> from the stable branch?
>
> The reason I bring this up is that there have been various points when
> bugs found in version 2.0 have been fixed in the CVS repository, but
> that repository has been unsuitable for production (due to the addition
> of new features and the refactoring of existing designs). While it's
> always possible to fetch the original 2.0 code and patch it up to fix
> the bug, it would be much easier to users of jBoss if the could simply
> get version 2.0.1
>
> I think that jBoss 2 was a production-ready release, and was rather
> surprised that full scale development continued after its release
> without any mechanism like this to allow bugfix releases in the interum.
>
> This lack of a 'stable branch' (if you will) also makes it more
> difficult for me to advocate the use of jBoss for a production
> environment - telling my boss (who has a technical background) "jBoss is
> a great development environment and the releases are really solid." will
> lead to the question "How are they about bugfixes." OK, I can answer
> "Well, I can patch up the production server!" won't quite cut it. Having
> that discussion with a client could be a career limiting move.
>
> Please understand that I mean no criticism of the good work that all of
> the JBoss developers are doing, and I hope you understand my regrets
> that I haven't had the time to contribute materially myself. I do think
> that by adopting a bit of formality in terms of development vs. stable
> releases, we (the jBoss community) can make the jBoss suite of tools far
> more compelling to a far wider audience.
>
> peace, love, and Good Code,
> danch
