UPDATE 28-05-2009 – Release of JBoss AS 5.1 has made this blog post obsolete and because I don’t longer feel any urgency nor think that is appropriate to comment on RedHat release or quality control process I’ve decided to retract the text.
Categories
- cloud (4)
- design (2)
- jboss (9)
- Administration (3)
- microcontainer (2)
- seam (2)
- Uncategorized (3)
4 Comments
WRT ‘plague of jars’ & “But there is not going to be a bug fix release. Next scheduled version is 5.1″
Not true.
5.0.1 is coming out in a few days (~14),
with the fixes to most pesky bugz,
temp jars plague being one of them. ;-)
Thank you Ales, my observation was based on Dimitris comment
‘Move the fix to 5.1.0. There won’t be a 5.0.1 release.’
Re: the next release confusion.
Since JBoss 4.2 we’ve taken compatibility between releases very seriously, i.e. we strive to make a point release upgrade (e.g. 4.2.2 -> 4.2.3) as painless as possible, ensuring that the application developer will have to make minimal to zero changes to his application/deployments.
So initially, while I had planned for 5.0.1.GA, some developers proposed that a couple of changes/features added to the branch might not be 100% compatible so we should go for a 5.1 instead. But then, we realized it’s more important to address the initial glitches of AS 5.0 rather than introducing anything new, so 5.0.1 would become the priority. This bug fixing release should be out really soon (end of Jan).
I’m not sure the release of AS5 warrants a retraction; it’s good to see such detailed community interest.
S,
ALR