Difference between revisions of "Category:RoadMap"

Roadmap calendar

This page describe what are the standard release policies.

Number of releases per year:

• Major releases: 2
• Minor maintenance releases: N (depends on bug reports and importance)

Dates are (YYYY is current year, YYYY+1 is next year):

* January YYYY   - Major Release (version A.B.0)
* March YYYY     - Start Major beta (version A.B+1.0): Freeze. Creation of branch A.B+1. See definition of freeze later.
* June YYYY      - Major Release (version A.B+1)
* October YYYY   - Start Major beta (version A.B+2.0): Freeze. Creation of branch A.B+2. See definition of freeze later.
* January YYYY+1 - Major Release (version A.B+2.0)

* At any time during year YYYY, maintenance fix releases (version A.*.N) of stable branch (A.*).

Let take an example :

* January 2013        - Major Release (version 3.3.0)
* 1st of March 2013   - Start Major beta (version 3.4.0): Freeze. Creation of branch 3.4.0. See definition of freeze later.
* In march 2013       - Mainteance release 3.3.1 was released. See definition of maintenance version later.
* June                - Major Release (version 3.4)
* 1st of October 2013 - Start Major beta (version 3.5.0): Freeze. Creation of branch 3.5.0. See definition of freeze later.
* January 2014        - Major Release (version 3.5.0)

All new features have to been push into develop branch.

Freeze definition

When we make a freeze of code, it means we start the beta period. It does not means that we must not change the code. It means that we can do some thing, and we can't for some other. This is generic definition of a Freeze.

• A freeze is done with a goal of a stable version in mind.
• When a freeze start, all following things are still allowed:
  • Any change of code to fix bugs
  • Any change into translation (language files or adding key implementation)
  • Any change into data reference (stored into table llx_c_*. For example, update of vat rates, adding countries, ...)
  • Any change to finish works that was started before the freeze.
  • Any change into theme or looks (change into HTML to match W3C, or CSS changes).
• The following things are not allowed:
  • Any change into architecture.
  • Adding or removing new external libraries.
  • Adding new features (However, adding a component whose code is isolated from rest of code like submodules "boxes" or "emailing target selector" may be accepted by project leader).

Maintenance definition

When a stable version is released, the branch become a maintenance branch. This means, a lot of things can not be done into this branch anymore. This is generic definition of a maintenance branch.

• A maintenance branch is called x.y.* (* start to 1 and is increased for each new maintenance version).
• Only changes to fix "blocking", "annoying" or "security" bugs can be done. Bugs making a new feature not available (when feature was never available) must not necessarly be fixed. It 's just a feature not yet ready into this branch, it will be available with next branch.
• There is an exception: We can add backported code of version x.y+1 into a maintenance branch to prepare transition for modules developper, but only if code added is a complete new method or new fonction, with no other change.

List of past versions

This Roadmap page is an index of all dedicated pages to RoadMap of each version (past and future).

Cette page Roadmap est un index de toutes les pages RoadMap de chaque version (passée et future).

Esta página Roadmap es un índice de todas las páginas dedicadas al RoadMap de cada versión (pasadas y futuras).