chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Klevenz, Stephan" <>
Subject RE: Release 0.1.0-incubating preparation
Date Mon, 14 Jun 2010 11:14:29 GMT
Hi all,

Sorry for my silence the last couple of days but I was absence because of private reasons.

No I'm back for contribution :-) and have updated issues relevant for me.


-----Original Message-----
From: Florian Müller [] 
Sent: Montag, 14. Juni 2010 10:22
Subject: RE: Release 0.1.0-incubating preparation


Can we ask all reporters and assignees of OpenCMIS issues [1] to assign the issues to releases?
There are only 7 issues and 4 people involved (Jens, David, Florent and Stephan).

- Florian


-----Original Message-----
From: Gabriele Columbro [] 
Sent: Sonntag, 13. Juni 2010 17:27
Subject: Release 0.1.0-incubating preparation

Hi guys,
on this not really sunny Sunday in Amsterdam I found some time for  
working a bit on the 0.1.0-incubating release.

Looking at [1], couple of heads up:

- As suggested in the "Open issues" section,  I went trough Jira and  
found actually all issues "unscheduled".  So I created few possible  
versions in Jira [2]  (0.1.0, 0.1.1, 0.2.0, 1.0.0) so we can schedule  
the issues to proper release. I added opencmis-* in version names, as  
I suppose ofther chemistry hosted projects will follow different  
release schedule and version scheme. Do you think is there any  
specific issue should include/fix it in 0.1.0 or shall we just  
reschedule them it to the version that looks more reasonable?

- I'm also trying to understand what would be the best / easy /  
reproducible way to integrate our release process with the standard  
maven based projects staging [3], in a way that in the same process we  
could distribute the aggregated artifacts [4] via standard 
  and the single JARs (useful to to application builders) via the  
standard maven staging process. I just created a branch for that [5].  
Will keep you posted if I get any quick result here or otherwise  
proceed with the existing.

Thanks for any feedback,




Gabriele Columbro
Alfresco Software, Ltd.


View raw message