Launch

New IPT Version Launch Procedure

Pre-release steps:

1. Label all issues related to version
   • Label issues with issue type (bug, enhancement, duplicate, won't fix, task, other, etc.), used in statistical reporting.
   • Assign milestone to each issue, used to group all issues addressed since last version was released. For example, here are all issues addressed in version 2.3.5.
   • Assign project to issues worked on, used internally and externally to transparently show work done for this version. For example, here is the project for 2.3.5.
2. Finalise work
   • Work on each issue should be considered "Done". The meaning of "Done" being understood and agreed on by the entire team, but ideally this also includes having written automated testing and performed manual (UI) testing.
3. Finalise translations
   • Work translating each language (by volunteer translators in Crowdin) should be both 100% translated and approved.
   • The translations should be exported from Crowdin and committed to the IPT repository following the instructions found in each properties file, e.g. ApplicationResources_fr.native.
4. Test release candidate
   • Test new features
   • Test areas

Release steps:

1. Release new version using Jenkins
2. Update GBIF IPTs to new version
3. Update User Manual
4. Update release history
5. Create/update Release Notes
6. Publish blog post
7. Update GBIF.org
8. Announce to IPT Mailing List
9. Broadcast on social media
10. Reward volunteers