Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RoleAssigneeAuthority/Responsibility
Release ManagerSPH"owns" release, initiates process, creates tracking page, sends daily status updates, tracks issues to completion, makes sure everyone gets their stuff done, brings decisions to CCB/team, maintains tracking page, collects lessons learned, documents process improvements for next release. Must be reachable and preferably in the office during critical stages like creating and testing RCs.
Build ManagerJJKP or LOJ(?)controls build system, creates RCs, sends RC availability announcements. Must be reachable and preferably in the office during critical stages like creating and testing RCs.
Test ManagerTRcontrol GUI/script testing for each RC.  Must be reachable and preferably in the office during critical stages like creating and testing RCs.

...

TaskWhoStatus

Internal

Status

Notes

Review Previous Build Release R2015b Process Notes

All   
Obtain Release ApprovalsSPHDoneDoneNeeded by release day.
Get updated legal statement/licenseSPHDoneDoneNeeded by Code Freeze.
Update sample scripts
SPHDoneDone

Needed by App Freeze.

  • Write examples that demonstrate new functionality
  • Clean up all errors and warnings
  • Remove deprecated fields
Write draft Release Notes

JJKP

SPH

DoneDone

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPHDoneDone

Needed by App Freeze.

Will be used in User Guide, websites, release announcement.

Update version number in User Guide cover
JJKPDoneDone

Needed by App Freeze.

Contact Katy Gammage or Mary Hrybyk-Keith to update cover page.

Next time: integrate sejda-console to do this automatically.

Update info on public-facing websitesJJKP(error)(error)

Needed by Release Day.

See the list of sites. Update this list as well, if necessary.

Updated major sites before announcement. Minor ones can be updated a bit later.

Update release announcement contactsSPH  

Needed by Release Day. Located here.

Put in order for additional iconsSPHDoneDone

(if necessary)

Needed by Visual Freeze.

For QA Complete (

...

July 10)

QA complete means that all known bugs are being tracked, all bug fixes are verified and documented, and the release process can begin.

...

TaskWhoStatusNotes
Verify that all known bugs are checked into JIRA(All)

JJKP: (tick)
RQ: (tick)

SPH:  (tick)

 
Complete all JIRA verifications(All)

JJKP: (tick)
RQ: (tick)

SPH:   (tick)

 
Complete QA wrap-up tasksDJC, SPH, JJKP, RQ

JJKP: (error)
RQ: (tick)

SPH:  (tick)

DJC: (tick)

JJKP: Need to run save mode one last time before code freeze.
Address all JIRA tickets awaiting feedback(All)

JJKP: (tick)
RQ: (tick)

SPH: (tick)

 
Mark .tc files with requirements and verify traceability to new requirements(All)

JJKP: (error)
RQ: (tick)

SPH: (error)

This is new this year! 

For Visual Freeze (

...

Aug. 5)

Visual Freeze finalizes all graphical changes to the software, so that screenshots, documentation, and TestComplete can be updated.

...

TaskWhoStatus

Internal

Status

Notes
Update About panel

LOJ

 (tick)(tick)
  1. Update release number (i.e. R2015a).  
  2. Add any new libraries used. 
  3. Update an links.
Update splash screenTGG(tick)(tick)
  1. Add new contributors
  2. Remove contributors who did not contribute to this release
  3. Design updates
  4. Update SplashScreen.psd in GmatDevelopment\moredata\graphics\splash
  5. Use GIMP to save a flattened TIF file and overwrite splash screen in GmatDevelopment\application\data\graphics\splash.
Update iconsTGG

SPH: (tick)
WCS: (tick)

TGG: (tick)

SPH: (tick)
WCS: (tick)

TGG: (tick)

If there are any updates, additions, deletions.

Including GMATIcon for Welcome Page

Update gmat_startup_file.txtJJKP(tick)(tick)
  • Update formatting, comments
  • Add any additional plugins
  • Switch to release configuration (comment out alpha plugins)

Switch to release configuration in script test system

JJKP(tick)(tick)
  • Create new rundef.R2015aInternal.template.m and rundef.R2015aPublic.template.m.
  • Switch autorun.m to use appropriate one.
Complete visual updates(All)

SPH: (tick)

RQ: (tick)

  

For Code Freeze (

...

Aug.

...

5

Code Freeze is a freeze on the software itself before final testing.

...

Warning

(DJC here)  A better approach going forward would be to merge master into production, and switch the test system to the production branch.  This probably ought to be done right before building RC1.  The dev team would have 2 options then:

  1. Checkout branches based on what they are working on (i.e. checkout production for bug fixes for the release, and their current clone of master – every one is cloning for new work, right? – for ongoing work)
  2. Alternatively, make bug fixes in master and cherry-pick merge changes into production as bugs are fixed

The former is the better approach, IMO, because it ensures that the bug fix is made on the current code base for the release.

For App Freeze (

...

Aug. 5

App Freeze is a freeze on all application bundle files beyond data and code. This includes documentation, sample scripts, stuff in the extras folder, etc.

...

TaskWhoStatusNotes
Update README.txtJJKP (tick)Update with major release highlights.
Update extras folderJJKP (tick)Notepad++ syntax coloring file
Update PDF files in docs folderSPH/DJC

DJC: (tick)

SPH:  (tick)

  • Update watermark: "Draft for Release R2015a"
  • Put into application/docs folder, and individual doc source folders
Gather list of compatibility changes since last releaseSPH (tick)
  • Deprecated fields
  • Removed & disabled fields
  • Anything a user would need to know to make R2013b scripts compatible with this release.
Update Release Notes
SPH (tick) 
Update screenshots in User Guide
(Feature leads)

JJKP: 

SPH: (tick)

RQ: (tick)

DSQ: 

 
Test User Guide instructions & code(Feature leads)

RQ: (tick)

DSQ: 

JJKP: 

SPH:  (tick)

  • Tutorials
  • Common Tasks
  • script snippets
  • reference page examples

SPH:  only tested features that changed for which I was FDE

Update Windows installer packageJJKP (tick) 
Update links in GMAT.ini

JJKP

(tick)
  • Help links
  • Welcome page links
Update link tests in TestCompleteTR (tick)
  • Help buttons
  • Welcome Page links
  • Help menu links

Testing of Release Candidate 1 (

...

Aug. 15 - Sep. 15 )

This will start with the 2014-05-05 daily build. Repeat this phase until tests check out. Steve will make the call.

...

Info
titleNotes
  • While this cycle is ongoing is a good time to do wiki updates and cleanup.

Stage Release (

...

Sep. 25)

This is a soft release, putting all the files in place and updating information. Then on release day, we only need to send the announcements.  

...

* DJC can only do steps 1-3 here because of contractual constraints

Release Day (

...

Sep 30)

Use "(/)" for the checkmark ((tick)) and "(x)" for the cross ((error))

...