What I'm really getting at, is there some branching scheme in CVS so
that bug fixes can be merged into a 2.0 branch or something, so that
problems with 2.0 can be fixed while the next major release is being
developed on? Or is there only a rolling "mainline"?
BTW, having something as simple as a release schedule isn't much of a
commitment and isn't something you should have to pay for. Why wouldn't
the JBoss folks set a date for a feature freeze so that they can release
the next version of JBoss? Many other open source projects do the same
and it shows how well the open source project is managed. If the JBoss
folks actually want people to use JBoss in production, there should be
some scheme for obtaining bug patches and releases. If there already is
some scheme for this, please let me know.
Also, I thought the currency of the Open Source movement wasn't money,
but rather contributions. Your talk of paying $25,000 is total shite.
I wouldn't being porting our mature Weblogic application to JBoss if I
had to pay for anything.
Bill
Peter Routtier-Wone wrote:
>> What's the release schedule for the next version of JBoss? Is there any
>> document/email anywhere that details it's new features?
>
>
> This is open source software. There isn't a release schedule. You have to
> pay people if you want commitments like that. An interesting point that
> should be made is that even with an open source project you can pay for such
> commitment. If your company really wants EJB features as soon as possible, a
> cash donation of say $25,000 -- half the price of a single BEA Weblogic
> deployment licence -- along with the list of the things that you need
> soonest, is a very effective way to engage the sympathies of an open source
> community. It is much more effective than "hurry up and give me something
> for free" -- which for an obviously absurd request is surprisingly common.
>
> As for features, EJB 2.0 is the defining document, and it isn't finished.
> This is outside of the hands of the JBoss community. Which is not such a bad
> thing. The lull in the addition of new features is allowing consolidation of
> the code base.
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
>
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
