These pages describe how we plan features to releases.
Where to go next
Best start with the small overview at Planning and Release Process Overview
Understand inspectIT release processes:
- Understand Release planning: When do we release?
- Understand which different Release types that we support in inspectIT. Having these different release types allows us to ship features and fixes faster to our customers.
- We have a clear definition of Ticket types and severity. The ticket types differentiate between internal and external visible tickets which is important to the creation of Release Notes
Understand the mapping of the release process to the tools we are using
- Jira Release Mapping
- We intend to start all releases from our Continuous Integration server. Each release type needs additional tasks that are carried out by the release process.
Background
We adapted our - already automated - release process of inspectIT to automate also the organisational tasks. We identified the following problems with our old release process.
- We never know when we release
- We just keep moving the date further and further, the end users never know when they get a version
- We have the feeling that a release is very timeconsuming and that there is so much manual stuff to be done
- We have problems specifying what we did
- We cannot deliver our features and fixes that we already finalized