Hi All,
There was some ambiguity in which version of the quick-look tests to run
before check-ins, so we wanted to clarify the check-in requirements ...
*The mandated check-in requirements are: *
* * A separate person to review the changes, *
* * PE and EE quick-look tests run with all tests passing
*
o *This requires setting up a cluster profile
(glassfish/bootstrap: maven configure-cluster)*
o *Running the PE and EE quick-look tests
(glassfish/appserv-tests: maven runtest-ee
*
* * A bug/RFE number *
* * A short description of the change documented in the check-in
comments.*
o * A bug number isn't enough to make quick sense of CVS logs
for merging, please cut and paste the Synopsis/Summary of
the related bug/RFE into the check-in comments at a minimum.*
*
Please Note:*
* The SJSAS91_UR1_BRANCH will be merged back into the
SJSAS91_FCS_BRANCH for inclusion into the Glassfish V2.1 Release,
so separate check-ins should not be required. The merge will be
performed by the module leads.
* If the check-in also pertains to the Trunk a separate check-in
will be need to be completed there.
* Soft code freeze is midnight PST 10/30/07
* Hard code freeze is midnight PST 11/13/07
This release is scheduled over the Holidays, so please check-in your
approved changes as soon as possible to avoid any last minute fires in
your areas that could potentially interrupt the celebrations.
For more information please see the Glassfish V2 Update 1 Project Wiki
page <
http://wiki.glassfish.java.net/Wiki.jsp?page=PlanForGlassFishV2UR>.
Please let us know if you have any questions or concerns...
Thanks for your cooperation - Mark & Shreedhar :-)