You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Release Cadence & Phases


Major Releases...

Consist of:

  • Feature development (minus 4 months to minus 4 weeks)
    • New features, changes and enhancements to existing features, and/or bug fixes.
  • Integration period (minus 4 weeks to minus 2 weeks)
    • Milestone: Feature Freeze at release minus 4 weeks.
    • Integration, QA and testing of the different contributions.
  • Release Candidate period (minus 2 weeks to minus 1 day).
    • Milestone: The RC0 build.
    • During RC Period, fix blocker & critical defects. Other defects deferred to next cycle.
    • New blocker and critical bugs will be fixed and will trigger a new RC build.
    • Release Criteria: no blocker or critical defects.
    • End of Release Candidate Period (day before release date)
  • Major Release (release date)
    • Milestone: Release
    • Build the new release
    • Major Release goes live and is available to download
      During RC Period, fix blocker & critical defects. Other defects deferred to next cycle.
    • New blocker and critical bugs will be fixed and will trigger a new RC build.
    • Release Criteria: no blocker or critical defects.
    • End of Release Candidate Period (day before release date)


Release Naming

The release names are YY.MM – for example, the first ODIM release is January 31, 2021 and it is named 21.01.

Defect Severity and Definition

Severity

Definition

Blocker

Showstopper! The highest level of your prioritization schema. Everything possible needs to be done to solve this issue.

Critical

Crucial issues that block the customer from performing some functionality, making the software unusable.

Major

Mostly important, but neither critical nor a showstopper.

Minor

Not very important, but still bringing some benefit that should be considered for implementation



  • No labels