2014.0/Release plan

From Wiki [en] OpenMandriva
< 2014.0
Revision as of 15:17, 1 December 2013 by TPG (Talk | contribs) (add dates)

Jump to: navigation, search

Basic rules

Some simple rules to follow:

  • Releases should happen on fridays – this may sound a little bit odd but good things starts on

weekend :)

  • No serious software breakages - this release needs to be done smooth and quickly
  • Follow rule "if you break, you fix it or revert to working EVRD"
  • Before release day on TC meeting (tuesday preferred) each TC member express each own point on

GnG situation

  • Final GnG decision is for QA
  • Release manager should keep dates
  • Each release we need to have a good press announcement on all available media, like own site, own

social channels (fb, twitter, others), other main *NIX related sites (distrowatch, phoronix, others), as much as possible is more than welcome :)


KPI

Below are dates and KPIs (key performance indicators) for a 2014.0 release Total amount of bugs filled for OpenMandriva 2014.0 on http://issues.openmandriva.org

Bug severity
Release stage Amount of blockers Amount of criticals Amount of majors
RC1 0 <=2 <=15
RC2 0 0 <=10
Final 0 0 <=5
Bug importance
Release stage Amount of highest Amount of high
RC1 <=10 <=10
RC2 <=10 <=10
Final 0 <=5

Dates

Release of Alpha stage - release date 2014-01-31

  • ISO needs to be released on 2014-01-26 - responsible is Release Manager
  • QA starts veryfiyng ISO for new issues.
  • On TC meeting on there will be a decision for GnG for release RC1
  • After "GO" an announcement on this release needs to be released to public on day.

Release of Beta stage - release date 2014-02-28

  • ISO needs to be released on 2014-02-23 - responsible is Release Manager
  • QA starts veryfiyng ISO for new issues.
  • On TC meeting on there will be a decision for GnG for release RC1
  • After "GO" an announcement on this release needs to be released to public on day.

Release of RC1 stage - release date 2014-03-21

  • ISO needs to be released on 2014-03-16 - responsible is Release Manager
  • QA starts veryfiyng ISO for new issues.
  • On TC meeting on there will be a decision for GnG for release RC1
  • After "GO" an announcement on this release needs to be released to public on day.

Release of RC2 stage - release date 2014-04-04

  • ISO needs to be released on 2014-03-30 - responsible is Release Manager
  • QA starts verifying ISO for new issues.
  • On TC meeting on there will be a decision for GnG for release RC2
  • After "GO" an announcement on this release needs to be released to public on day.

Release of FINAL product - release date 2014-04-18

  • ISO needs to be released on 2014-04-13 - responsible is Release Manager
  • QA starts verifying ISO for new issues.
  • On TC meeting on there will be a decision for GnG for release Final Product
  • After "GO" an announcement on this release needs to be released to public on day.

Tasks for FINAL release

TODO

Roadmap

20140 release plan.png