Changes between Version 28 and Version 29 of DevNotes/Processeses/DeploymentProcess


Ignore:
Timestamp:
Feb 15, 2019 10:17:06 PM (5 years ago)
Author:
butler
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • DevNotes/Processeses/DeploymentProcess

    v28 v29  
    1414 
    1515== Testing a new major release == 
    16 Besides the ongoing testing with every pull request, extra care in testing should be taken for a major release. A first step should be for the developers (and any identified "friendly users" to install the master build from Jenkins and thoroughly test.  It is recommended that an actual beta pre-release be published on github to broaden the nunber of testers. 
     16Besides the ongoing testing with every pull request, extra care in testing should be taken for a major release. A first step should be for the developers (and any identified "friendly users") to install the master build from Jenkins and thoroughly test.  It is recommended that an actual beta pre-release be published on github to broaden the number of testers. 
    1717   All bugs and issues identified during this testing phase will be ticketed and either fixed or discussed on the conference call to ascertain if they must be fixed (blockers) or can remain known issues to be reported in release notes and fixed in a future release. 
    1818Once everyone agrees that the master build is ready, the release manager will start the final release process.