Eric Lau wrote:
> Althought I agree that a release schedule would be nice, writing a release schedule
>should be to the discretion of the developers. If you are looking for a certain
>feature, maybe you could contribute code or write to the developers directly or try
>the developer mailing list.
Again, what I was really getting at was that there really needs to be a
CVS branch for 2.0 bug fixes so that those of us who are going to use
JBoss in production can contribute and receive bug fixes to the existing
stable release rather than have to worry about a possibly unstable
latest/greatest build. If there already is such a branch, please let me
know! I've already run into a Mailing-List documented known-problem,
that is fixed in the daily drop of Jboss, but not in the current
2.0Final release. I really don't mind finding and fixing bugs in 2.0 on
my own. It would just be nice to be able to merge these fixes to a 2.0
branch and not a re-designed (untested?) product with tons of new
features like the current source looks like it is. In fact, I would
volunteer to maintain this branch if you could allow me to come up to
speed on CVS, and walked me through any testing procedures that are done
on the product.
>
> I think the currency of Open Source is contribution, which is not limited to money,
>but I don't think it precludes it. If jBoss is not good enough for you, ie. you
>wouldn't be paying for it if it wasn't free, then maybe you are better off using
>WebLogic or whatever fits your purpose best.
Please don't misinterpret me. I think JBoss is great. Much faster than
WebLogic and more standards compliant! Plus its nice having the source
code. But porting from WebLogic to JBoss is a considerable effort
(engineering time = money) and if we had to pay as much for JBoss as
Weblogic, the effort just wouldn't be worth it.
Bill
>
> Cheers
>
> Eric
>
> #####
> Opinions are mine and does not reflect the view of my employer.. yada yada
> #####
>
>
> On 0, Bill Burke <[EMAIL PROTECTED]> wrote:
>
>> 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]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
>
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
