v3 Developers,
The first build from the TP2 branch (b10) was promoted this morning.
While the build is being tested, please continue to scrub P1 and P2 bugs
in your areas. Our goal is to address all P1 bugs before our release.
Here is the link to open defects for TP2 release --
Open P1 & P2 Defects for TP2 Release
<
https://glassfish.dev.java.net/issues/buglist.cgi?issue_type=DEFECT&component=glassfish&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&priority=P1&priority=P2&version=V3&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=fulltext&long_desc=&long_desc_type=fulltext&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=tp2-exclude&keywords_type=notokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query>
To ensure stability of the build, check-ins to TP2 branch are restricted
to "showstopper issues" for the release. Please use the following
guidelines while scrubbing the bugs.
1. If it is P1, it should be fixed. See Kohsuke's e-mail
<
https://glassfish.dev.java.net/servlets/ReadMsg?list=dev&msgNo=6736>
for branch build instructions. In addition to peer code review,
please get your change approved by Jerome.
2. If it is P2 and a showstopper (i.e. must be fixed for TP2 to avoid
significant impact on users), please contact Jerome to get an
approval to fix the bug. Once Jerome approves, the same rule as
"P1" bugs apply.
3. For all other P2 bugs (that are not showstopper), please update
the issue and add the keyword "tp2-exclude". (note keyword is
different from status whiteboard on issue tracker).
Just to reiterate, the above rules apply only to TP2 branch, you can
continue to fix all bugs on the svn trunk. Also, when you fix a bug on
the branch, please apply the fix to the trunk.
Thank you,
Abhijit