Skip to main content
Jump to: navigation, search

Difference between revisions of "MoDisco/Version Numbering"

(Guidelines)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Version numbering of components in MoDisco platform.
+
Version numbering of components in the MoDisco platform.
 
+
  
 
== Initial contribution ==
 
== Initial contribution ==
  
Depending on state of your component, version numbering will start at 0.1.0 or at 0.6.0.
+
Depending on the state of your component, version numbering will start at 0.1.0 or at 0.6.0.
  
The requirements to start at 0.6.0 are explained in following section, if your component doesn't match these requirements, version numbering of your component will start at 0.1.0.
+
The requirements to start at 0.6.0 are explained in the following section; if your component doesn't match these requirements, version numbering of your component will start at 0.1.0.
* Your component has been developped at least one year before its submission in bugzilla.
+
* Your component has been developed at least one year before its submission in bugzilla.
* Your component has been developped less than one year before its submission in bugzilla, but it has been widely used and tested in various environments.
+
* Your component has been developed less than one year before its submission in bugzilla, but it has been widely used and tested in various environments.
  
 
== Guidelines ==
 
== Guidelines ==
  
Main guidelines of MoDisco components are explained in [[Version_Numbering| eclipse rules]].
+
The main guidelines of MoDisco components are explained in [[Version_Numbering| eclipse rules]].
  
However, MoDisco is an incubation project, and one of incubation phase constraint is that version number of component shall be less than 1.0.0.
+
However, MoDisco is an incubation project, and one of the constraints of the incubation phase is that components version numbers must be less than 1.0.0.
  
And during incubation phase, to differentiate internal states of MoDisco components, we encourage to use this convention:
+
And during incubation phase, to differentiate internal states of MoDisco components, we encourage the use of this convention:
 +
* version numbers less than 0.6.0 are considered as initial contribution, or component in specification phase or partially implemented.
 +
* version numbers greater than or equal to 0.6.0 and less than 1.0.0 are considered as reaching completion.
  
* version number less than 0.6.0 are considered as initial contribution, or component in specification phase or partially implemented.
+
[[Category:MoDisco]]
* version number equals or more than 0.6.0 and less than 1.0.0 are consireded as reaching completion.
+

Latest revision as of 04:54, 13 January 2010

Version numbering of components in the MoDisco platform.

Initial contribution

Depending on the state of your component, version numbering will start at 0.1.0 or at 0.6.0.

The requirements to start at 0.6.0 are explained in the following section; if your component doesn't match these requirements, version numbering of your component will start at 0.1.0.

  • Your component has been developed at least one year before its submission in bugzilla.
  • Your component has been developed less than one year before its submission in bugzilla, but it has been widely used and tested in various environments.

Guidelines

The main guidelines of MoDisco components are explained in eclipse rules.

However, MoDisco is an incubation project, and one of the constraints of the incubation phase is that components version numbers must be less than 1.0.0.

And during incubation phase, to differentiate internal states of MoDisco components, we encourage the use of this convention:

  • version numbers less than 0.6.0 are considered as initial contribution, or component in specification phase or partially implemented.
  • version numbers greater than or equal to 0.6.0 and less than 1.0.0 are considered as reaching completion.

Back to the top