Necessary (manual) tasks of the inspectIT team for each release
This page lists recurring tasks the inspectIT team needs to take care of within each version/release. Please note that most of these tasks are handled automatically by the Jenkins Release Publisher Plugin. For all other tasks, the release publisher should create JIRA tasks so that we do not forget to do that.
| Ticket Name | Tickettype | Description |
|---|---|---|
| Perform explorative testing | TASK | Explorative Testing |
| Upgrade guide | TASK | A Upgrade Guide migration guide has to be written in Confluence |
| Release description | TASK | The release description (see Release Notes) briefly highlights the features of this version |
| Update welcome screen features | TASK | Update the welcome screen |
| Upgrade Jenkins job release number | TASK | Update the default value of the release jenkins job to the this new version |
| Update the version within the Docker Files | TASK | Our docker images are built automatically as soon as a change is made to the GitHub Docker repositories. It is necessary to change the docker files to create the correct docker images. |
| Update inspectIT on Wikipedia | TASK | Find at https://de.wikipedia.org/w/index.php?title=InspectIT&stable=0&shownotice=1 - update the latest version |
| Publish Release Info on Reddit | TASK | On each release we need to create a reddit posting to increase the visibility. |