releaseplan

i-doit is continuously being developed. As well as the correction of known problems, the development of new functions lies at the forefront.

  • The Road Map shows which functions are planned and for which release.
  • The Release Plan gives information about the type and the chronological order of publications.

The release plan of i-doit version 1.0 differentiates between minor and major releases. A major release delivers new features and mostly significant developments, whereas in between the major releases, different minor releases contain improvements for stability and security, bug-fixing and other small improvements.

Version descriptions

The type of release is directly identifiable with the version description. So with a major release, two digits will be used and with a minor release, three digits will be used.

For example, a 1.0 or 1.1 illustrates a major release, whereas, for example, 1.1.4 illustrates a minor release within a 1.1 major release.

Releases

For the release of new versions, the following time schedules and rules apply:

  • Minor releases are published in a fixed pattern of four weeks.
  • Major releases are brought out at time intervals of every two to four months.

Updates

From a technical perspective, the Release Plan has two rules for updates:

  • You can skip minor releases
  • You cannot skip major release

Therefore, for example, it is possible to progress directly from 1.0.2 to 1.0.6, likewise directly from 1.0 to 2.0. It will always take into account all the steps in between. Minor and major releases are cumulative, i.e. they contain all the information about changes within the current stage (minor) or the previous major release

The following illustrates the principle: 

 

roadmap

This provides an overview of future features and functions of i-doit. We follow the dynamic development methodology SCRUM. The contents of this roadmap are generated automatically (updated daily) from our product backlog and shape of our SCRUM sprint. The roadmap is a reflection of our current planning at the present time. The planning for early releases is much more accurate than those that lie ahead. This will over time result in changes in prioritisation of issues and add further topics.

The listed functions to each version should be completed up to the respective version. For example:

The features listed below version 2.0 should be completed until version 2.0, so in versions 1.1, 1.2 ... 1.x. However, they are listed under the version 2.0 because there is still no accurate prioritisation.