search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Create one branch per every supported Alfresco release #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
In order to better support different Alfresco versions and releases, which 
might break compatibility with some parts of our archetypes, we'd better 
create one branch per each Alfresco major release (at least).

Currently we should provide at least 3.1 and 3.2 branches.

Original issue reported on code.google.com by carlo.sciolla on 16 Mar 2010 at 12:24

GoogleCodeExporter commented 9 years ago 
What do you think it should be the next target version?

At the moment (as I briefly tried to describe at 
http://code.google.com/p/maven-alfresco-archetypes/wiki/ProjectRoadmap) I see 
two main releases:

- A maintainance release for the current archetypes
- A new (Alfreso Swift compatible) release which maybe uses also Maven Calm?

Do we have the HP to manage per Alfresco minor version branches?

WDYT?

Original comment by colum...@gmail.com on 3 Aug 2011 at 11:57

GoogleCodeExporter commented 9 years ago 
Agreed. I started aligning version numbers already to Alfresco's one. I suggest 
that starting with 4x release, we maintain separate branches.

Original comment by colum...@gmail.com on 15 Nov 2011 at 5:28

GoogleCodeExporter commented 9 years ago 
Marked as task

Original comment by mauri...@session.it on 3 Apr 2012 at 10:19

GoogleCodeExporter commented 9 years ago 
The approach here radically changes with the Maven Alfresco SDK 1.0.

In fact a clear cut has been made between the lifecycle features, provided by 
the alfresco-sdk-parent, and the Alfresco distribution / release properties, 
provided by the Alfresco Platform Distribution POM (now delivered as part of 
each alfresco release 
https://artifacts.alfresco.com/nexus/content/repositories/releases/org/alfresco/
alfresco-platform-distribution/4.2.b/).

This way the lifecycle of the SDK is decoupled from the lifecycle of Alfresco 
and the compatibility different SDK versions might work against different 
Alfresco versions.

A compatibility matrix will be created to keep track of this.

Original comment by colum...@gmail.com on 29 Oct 2012 at 11:06