Something to note:
we need to make sure commits to Branch_5_0 are also ported to Branch_5_x and trunk, where
it
makes sense.
I've seen a few cases were changes were applied only, e.g. to Branch_5_0 and trunk so
they'll be missing from 5.1/EAP. I don't know if we can create a JIRA filter to
catch issues
fixed for 5.0.1.GA AND NOT 5.1.x
Also, the JMS examples, I don't think they belong to the AS source tree, they need to
be
moved to the documentation.
Jason T. Greene wrote:
5.1 Beta1
---------
Code Freeze: March 9th
Release: March 16th
The primary/required goal for this release is completion of all Profile
Service blockers, to facilitate the inclusion of the console:
https://jira.jboss.org/jira/browse/JBAS-6470
All other planned component updates for this release are located here:
https://jira.jboss.org/jira/browse/JBAS-6156
If one of these subtasks is assigned to you, and you can not complete
this in *2 weeks*, please let me know, so I can reschedule it to CR1.
Also please review the JIRA issues assigned to you and reschedule them
if you can not complete them for this release.
5.1 CR1
-------
Code Freeze: April 6th (Tentative)
Release: April 13th (Tentative)
The primary/required goal is inclusion of the embedded console. A
secondary goal is including JBM 2 as either an optional or main JMS
provider. These dates could slip a few more weeks depending on the
console timeline.
All major component upgrades need to be completed and in CR quality for
this release (with the exception of tech preview features.
5.1 GA
------
Code Freeze: May 4th (Tentative)
Release: May 18th (Tentative)
The primary/required goal is of course all tests (including TCK) cleared
and all assigned bugs resolved.
Any questions, feedback?