Hi Bill,
> 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"?
There is a "stable" and "development" release of JBoss - much like it is
with Linux. There is also a commited team behind JBoss working to add new
features and fix existing problems. If you have bug-fixs for version 2.0
that you wish to contribute please submit it to the list with a good
description of what it fixes and how. If it is important/useful then it will
be integrated into the JBoss 2.0 distro (and subsumed into the latest JBoss
as well).
> 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.
This is an open source project Bill and there really isn't any point in
setting such dates when the work is done on a volunteer basis. The release
"delays" for Mozilla/Netscape & Linux's 2.4 kernel is proof that such
commitments don't hold much water in open source land however well
funded/managed the project is. Come to think of it, it doesn't mean much in
closed-source land too since most projects miss theier deadline.
The modus operandi here is to release "when it's good and ready!". The best
we can all do is to contribute needed resources (ideas/technology,
funding/equipment, deliverables e.t.c) to help make the release happen
sooner.
> 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
JBoss is an innovatively designed J2EE app server with many pioneering
features (e.g. hot-deploy, dynamic proxies, JMX integration). If your only
reason for using JBoss is because it is free then you have made a poor
choice. I would advise keeping your mature app on WebLogic (it is a good
product). The JBoss community can then get on with producing the JBoss suite
of products for people who want/need capable and innovative, first-class,
100% Java, open source, J2EE app servers. That it is also free is a welcome
but minor bonus IMO.
Cheers!,
Micheal
PS Contributions are any resource that you provide and that the
team benefits from. That includes money Bill. I presume from
your reply that the JBoss Group should not be expecting a $25K
cheque anytime soon ;-)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
