NB68HighResistance
NetBeans 6.8 High Resistance
Contents |
- Repository (clone): http://hg.netbeans.org/release68 - (commits)
- HR fixes candidates - issues with 68_HR_FIX_CANDIDATE keyword
- Fixed issues - issues with 68_HR_FIX keyword
In order to better stabilize 6.8 FCS we will utilize HR process.
Dates
- HR starts on Nov 16 0:00am CEST time in main-silver - means all team repositories are in High resistance mode.
- release68 clone is created on Sat, Nov 21st. Announcement email is sent and team repositories are opened for integrations, once the clone is ready to be used.
- Only 68_HR_FIX bugs can be fixed in release6.8 clone
Process
Only stoppers P1 will be fixed during High Resistance mode. P1 and P2s filled after cut off date (11/12) are evaluated, P2s for stopper status. If any issue is evaluated as stopper :
- upgrade priority to P1 and ask QA for decision (email or add to CC)
- if QA agreed with stopper status , they will add Keyword 68_HR_FIX_CANDIDATE to issue
- proceed with fixing ...
Fixing - after 6.8 clone (21/Nov)
- integrate fix (into team repository/silver) -> leave issue as STARTED with TM=6.8
- verify fix by QE (build from team repository or silver/golden) -> add comment into the issue
- review fix by peer -> add comment into the issue
- sent an email to reviewersATnetbeans.org with following informations:
- Description of the bug (including IZ #)
- Impact assessment i.e. why it is a showstopper?
- Risk assessment i.e. why is it safe?
- Confirmation of peer code review and QE verification of fix
- Changeset info (for reviewing diffs)
- integrate fix into release68 clone and replace keyword 68_HR_FIX_CANDIDATE by 68_HR_FIX -> change issue to RESOLVED FIXED
- you can use hg transplant to cherry-pick a bug fix from team repository into clone
- or if the parent revision was in the clone, you can just pull & merge it
- details: HgHowTos#WorkingWithReleaseClones
Fixing of all priorities continues in trunk.
Terms :
- All P2s are evaluated for showstopper status
- HR fixes are only stoppers (P1s) selected by QE
- HR starts on Mon 11/16 0:00am
- Clone is used only for HR integrations
- When clone is created all repositories are opened for integrations.
- Builds from clone are done on demand
Fixing - before 6.8 clone ( before Nov 21st )
This process applied to fixing of stoppers between 11/16 - 11/20.
- integrate stopper P1 fix as usual (into team repository/silver) -> set issue as FIXED with TM=6.8 and replace Keyword = 68_HR_FIX_CANDIDATE by 68_HR_FIX
- sent an email to reviewersATnetbeans.org with following informations:
- Description of the bug (including IZ #)
- Impact assessment i.e. why it is a showstopper?
- Risk assessment i.e. why is it safe?
- Confirmation of peer code review and QE verification of fix
- Changeset info (for reviewing diffs)
- QE verifies the fix.
