SHOW:
|
|
- or go back to the newest paste.
| 1 | # Releases | |
| 2 | ||
| 3 | Releases are performed by one person with appropriate credentials to deploy the | |
| 4 | artifacts and upload the documentation. For a release to occur in Maven a number | |
| 5 | of things must be true. | |
| 6 | ||
| 7 | - The application builds without any errors | |
| 8 | - Repository clean - no uncommitted changes | |
| 9 | - Repository shared - no local changes unpushed | |
| 10 | - All unit tests pass | |
| 11 | ||
| 12 | Additionally the following conditions must be checked by the release manager. | |
| 13 | All of these are to be done after the last commit to be included in the release. | |
| 14 | If new commits go in to remedy issues that are found, all checks should be done | |
| 15 | again on the latest code base. | |
| 16 | ||
| 17 | - All issues with target == next version are not only resolved, but also closed | |
| 18 | - No known regressions from last release present in current build | |
| 19 | - No known regressions in features added since the last release | |
| 20 | - No inappropriate string literals shall be present in the code base | |
| 21 | - All localisation files complete and contain no English, except the English one | |
| 22 | - No commented out code shall be present in the code base | |
| 23 | - No SNAPSHOT versions shall be depended upon, including plugins | |
| 24 | - | - mvn install on mac produces working bin.jar, linux.zip, .deb, .exe, .dmg files |
| 24 | + | |
| 25 | - findbugs shows no serious issues and equal to, or less than the last release | |
| 26 | - Test data-log files load correctly and display correctly for all decoders | |
| 27 | - mvn install on mac produces working bin.jar, linux.tar.bz2, .deb, .exe, .dmg | |
| 28 | - Windows exe executes and displays properly on XP and 7 | |
| 29 | - Linux zip and deb function correctly and display properly on a variety of wms | |
| 30 | - Mac dmg and app.zip function correctly and display properly on 10.6 and 10.7 | |
| 31 | ||
| 32 | Note, issues listed for future releases beyond the release in question can, and | |
| 33 | likely are present in the code that is about to be released. This is normal and | |
| 34 | completely OK. | |
| 35 | ||
| 36 | # Platform Check List | |
| 37 | ||
| 38 | - Full-screen entry/exit for each platform | |
| 39 | - Button behaviour for each platform | |
| 40 | - Key bindings for each platform | |
| 41 | - | - Update the issue trackr |
| 41 | + | |
| 42 | - Panel sizes make sense and don't affect functionality | |
| 43 | ||
| 44 | # Post Release | |
| 45 | ||
| 46 | - Update all repos | |
| 47 | - Update the website | |
| 48 | - Update the issue tracker | |
| 49 | - Announce on forum and facebook | |
| 50 | - Tag SNAPSHOT version for git describe | |
| 51 | - git push --tags to all repos |
