Skip to end of metadata
Go to start of metadata

Version 1.0

With Maven SCM 1.0, we'll release at the same time all SCM providers available in trunk with 1.0 version too.

Post 1.0

After the 1.0 release, the  actual trunk will be splitin few trunks like that:

maven/scm
    |-- maven-scm-api
    |    |--branches
    |    |--tags
    |    |--trunk
    |-- providers
    |    |--maven-scm-provider-bazaar
    |    |    |--branches
    |    |    |--tags
    |    |    |--trunk
    |    |--maven-scm-provider-cvs
    |    |    |--branches
    |    |    |--tags
    |    |    |--trunk
    |    |    |    |--commons
    |    |    |    |--cvsexe
    |    |    |    |--cvsjava
    |    |--maven-scm-provider-svn
    |    |    |--branches
    |    |    |--tags
    |    |    |--trunk
    |    |    |    |--commons
    |    |    |    |--svnexe
    |-- pom
    |    |--branches
    |    |--tags
    |    |--trunk
    |-- trunks
    |    |--pom.xml  //This pom will allow to build all modules with one command

The release of each component will be independant, so we'll can provide patches on each providers without to release all.
maven-scm-api won't use a minor version and will be always like X.X (1.0, 1.1; 1.2, 2.0...)
Each provider versions will use the maven-scm-api version and the minor number for the provider release, so a provider that use maven-scm-api 1.1 will have versions 1.1.0; 1.1.1, 1.1.2...

With this process, it will be easy to add new provider and release a version of it in a short time, and we won't have lot of alpha/beta but minor version updates.

Fixed versions in jira

As we'll have releases by providers, we'll add in jira new versions in the same jira project. Versions will be:

  • maven-scm-api 1.0
  • maven-scm-api 1.1
  • maven-scm-provider-cvs 1.0.1
  • maven-scm-provider-cvs 1.0.2
  • maven-scm-provider-cvs 1.1
  • ...
  • No labels