Obsolete: Release Strategy

From ADempiere
Revision as of 06:14, 20 March 2010 by CarlosRuiz (Talk) (synchronizing with current resource availability)

Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.

This page has been conducted by the PMC Release Team.


Releases

Maintained Releases (LTS = long term support)

  • Cycle: one time per year, 2nd Monday of June
  • Next Release: 14th of June 2010
  • SVN: Release Repository, a tag will be opened for the version, and a branch will be opened to maintain it (eventually a patches branch will be open to ease release of patches)

Unmaintained Releases

  • Cycle: two times per year, 2nd Monday of October and February
  • Next Releases: 11th of October and 14th of February 2010
  • SVN: Release repository, a tag will be opened for the version

Short Term Release Strategy

  • triage > 400 bugs
  • create an inventory list of functionality to find out...
    • ... what is core
    • ... what is obsolete or underdeveloped
    • ... what is the status of each feature (if it's stable, or working with known problems, or non-working)
  • release LTS with inventory list (not status-tagged - we mean next releases won't have "alpha", "beta", "stable" tag; but instead they'll be accompanied with the inventory of features)

Obsoletion of functionality

  • features that are either incomplete or do not have a maintainer will be inactivated, or moved as extensions to be integrated by hand on implementations.
    Starting with:
    • HTML UI
    • Posterita
    • Content Management
  • if after one release inactive, the functionality still don't have a maintainer, we can consider deleting it from dictionary

Long Term Release Strategy

to be developed...