Code check-in process for Milestone 1

Testing :

All the MS1 deliverables need to be verified by the following tests before being checked in.These are relevant if you have modified GF code or you code would be in the default runtime path.

1. GlassFish PE QL tests
2. GlassFish dev tests for that particular area ( recommended by the module owner)
3. GlassFish SQE smoke tests ( if recommended by the module owner)

Please check for the nightly build status for the build following your checkin. You have time till Aug21 12:00 Noon IST/ Aug 20 11:30 PM PDT to check in code. Please do it much before that.

If there are no baseline results available for the devtests, do run them against the sailfin nightly without your changes. There should be no extra failures. In case there are additional failures in the devtests, do check with the module owners to make sure that they can be waived.

Module structure :

We will have a module structure that corresponds to the maven 2 directory structure. Make sure that your module builds individually, from the sailfin/bootstrap module.

DO NOT checkin changes to the sailfin/bootstrap module. Naman would do it on your behalf.Once you have made changes and tested it , send the diffs across to Naman so that he can integrate the changes.