Versions Compared

Key

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

...

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 (

...

Oct.

...

6

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.txtSPH

SPH:(tick)

WCS:(tick)

DJC:


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

DJC: (tick)

SPH:  


Waiting for final user guide.

  • Update watermark: "Draft for Release R2016a"
  • 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 R2016b scripts compatible with this release.
Update Release Notes
SPH (tick) 
Update screenshots in User Guide
(Feature leads)

 

SPH: 

RQ: 

DSQ: 

 
Test User Guide instructions & code(Feature leads)

RQ: 

DSQ:  

SPH:  

  • Tutorials
  • script snippets
  • reference page examples

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

Update Windows installer packageTGG  
Update links in GMAT.ini

TGG

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

Testing of Release Candidate 1 (

...

Oct.

...

7-

...

14 )

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 (

...

Oct 20)

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 (

...

Oct.21)

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

...