-
1. Re: jboss-as-7.0.2.Final should be tagged as beta
nickarls Sep 28, 2011 5:13 AM (in response to lesbleus2007)On Slashdot there is a saying "You must be new here" ;-)
Jokes aside, there are "hundreds" of libraries referenced in the AS. If only a "Final" lib could be used, bugs would be fixed at snail-pace (if ever). If someone would rename Remoting 3.2.0.Beta2 to 3.2.0.RockSolid, would it be better?
-
2. Re: jboss-as-7.0.2.Final should be tagged as beta
lesbleus2007 Sep 28, 2011 7:01 AM (in response to nickarls)You're missing the point.
As long as a product contains beta parts it IS in beta version (maybe beta-final in jboss parlance).
So either you replace all beta parts with a release version or the products keeps the beta tag.
Customers don't like to pay for a solution and find betas inside.
Just like I wouldn't like to crash my car to find out the tyres were for testing purpose ONLY!
-
3. Re: jboss-as-7.0.2.Final should be tagged as beta
nickarls Sep 28, 2011 10:11 AM (in response to lesbleus2007)I found that the community version har been worth every cent I paid for it!
-
4. Re: jboss-as-7.0.2.Final should be tagged as beta
jason.greene Sep 28, 2011 10:19 AM (in response to lesbleus2007)I don't see a need to change the process.
The beta labeling of those two projects has to do with API stability (whether or not users should expect it to change), not implementation stablity. This isn't a concern for the AS since its an implementation detail, and we expect it to change.
Also sometimes we might ship beta add-ons, since most of our community user base prefers as early access as possible. This is in contrast with the enterprise release of JBoss AS (EAP), which favors limited change and long-term support.
-
5. Re: jboss-as-7.0.2.Final should be tagged as beta
jason.greene Sep 28, 2011 10:21 AM (in response to nickarls)Nicklas Karlsson wrote:
I found that the community version har been worth every cent I paid for it!
LOL. I am still trying to figure out if that's a compliment or an insult!