You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Gabriele Columbro <ga...@apache.org> on 2010/06/13 17:27:20 UTC
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 www.apache.org/dist
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,
ciao!
Gab
[1] https://cwiki.apache.org/CMIS/opencmis-release-documentation.html
[2] https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310936
[3] http://maven.apache.org/developers/release/apache-release.html
[4] http://people.apache.org/~fmui/opencmis/
[5] https://svn.apache.org/repos/asf/incubator/chemistry/opencmis/branches/dev-maven-release
--
Gabriele Columbro
Alfresco Software, Ltd.
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz
Re: Release 0.1.0-incubating "expandProperties" build issue [SOLVED]
Posted by Gabriele Columbro <co...@gmail.com>.
Hey guys,
looking at http://ant.apache.org/manual/Tasks/replace.html it seems
that the "expandProperties" attribute was introduced in Ant 1.8.0.
I updated https://cwiki.apache.org/confluence/display/CMIS/OpenCMIS+Release+Documentation
to reflect this change in pre-req.
HTH,
ciao!
Gab
On Jun 16, 2010, at 5:32 PM, Gabriele Columbro wrote:
> Hey guys,
> while trying to run the release process (still the Ant one, to see
> it fully running and then try to mimic it in Maven) I'm having the
> following issue:
>
> /build.xml:90: replacetoken doesn't support the "expandProperties"
> attribute
>
> Leaving out the old Ant vs Maven build reproducibility discussion
> (which I'll try to sort out anyways), my build specs are listed below.
> Any hint here on which ant version I should use?
>
> Ciao and thanks in advance,
> Gab
>
> [1] http://incubator.apache.org/chemistry/opencmis-release-documentation.html
>
> ~~~o0o~~~
>
> zion:0.1.0-incubating mindthegab$ uname -a
> Darwin zion.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15
> 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 i386
>
> zion:0.1.0-incubating mindthegab$ ant -version
> Apache Ant version 1.7.1 compiled on April 8 2010
>
> zion:0.1.0-incubating mindthegab$ java -version
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-9M3165)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
>
>
>
>
>
> On Jun 14, 2010, at 2:14 PM, David Caruana wrote:
>
>> There are 68 issues fixed for the components chemistry-abdera, tck
>> and opencmis-*. I'll update their fix version to 0.1.0.
>>
>> Dave
>>
>> On 14 Jun 2010, at 09:55, Jukka Zitting wrote:
>>
>>> Hi,
>>>
>>> On Sun, Jun 13, 2010 at 5:27 PM, Gabriele Columbro <gabriele@apache.org
>>> > wrote:
>>>> I added opencmis-* in version names, as I suppose other chemistry
>>>> hosted projects will follow different release schedule and version
>>>> scheme.
>>>
>>> An alternative is to create new Jira projects like CMISPHP for
>>> codebases that follow a separate release schedule. Many of the Jira
>>> reports assume that a single Jira project maps to a single release
>>> schedule.
>>>
>>>> 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?
>>>
>>> The already resolved issues that affect the OpenCMIS codebase should
>>> probably be marked as resolved for 0.1.0. This will make the Jira
>>> release reports more effective.
>>>
>>> I'd leave unresolved issues unscheduled unless they're explicitly
>>> being targeted for a specific release.
>>>
>>>> - 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 www.apache.org/dist and the
>>>> single
>>>> JARs (useful to to application builders) via the standard maven
>>>> staging
>>>> process.
>>>
>>> In Jackrabbit we use an assembly and some custom Ant tasks to stage
>>> the release artifacts targeted for www.apache.org/dist. See the
>>> apache-release profile settings in the Jackrabbit reactor POM [1].
>>>
>>> [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
>>>
>>> BR,
>>>
>>> Jukka Zitting
>>
>
> --
>
> Eng. Gabriele Columbro
> Alfresco Software, Ltd.
>
> M: +31 (0)627 565 103
> P: +39 320 161 28 46
> D: +44 (0)1628 876 654
>
> Skype: gabrielecolumbro
> Blog: http://www.mindthegab.com
> Twitter: http://twitter.com/mindthegabz
>
>
>
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz
Release 0.1.0-incubating "expandProperties" build issue
Posted by Gabriele Columbro <co...@gmail.com>.
Hey guys,
while trying to run the release process (still the Ant one, to see it
fully running and then try to mimic it in Maven) I'm having the
following issue:
/build.xml:90: replacetoken doesn't support the "expandProperties"
attribute
Leaving out the old Ant vs Maven build reproducibility discussion
(which I'll try to sort out anyways), my build specs are listed below.
Any hint here on which ant version I should use?
Ciao and thanks in advance,
Gab
[1] http://incubator.apache.org/chemistry/opencmis-release-documentation.html
~~~o0o~~~
zion:0.1.0-incubating mindthegab$ uname -a
Darwin zion.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15
16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 i386
zion:0.1.0-incubating mindthegab$ ant -version
Apache Ant version 1.7.1 compiled on April 8 2010
zion:0.1.0-incubating mindthegab$ java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-9M3165)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
On Jun 14, 2010, at 2:14 PM, David Caruana wrote:
> There are 68 issues fixed for the components chemistry-abdera, tck
> and opencmis-*. I'll update their fix version to 0.1.0.
>
> Dave
>
> On 14 Jun 2010, at 09:55, Jukka Zitting wrote:
>
>> Hi,
>>
>> On Sun, Jun 13, 2010 at 5:27 PM, Gabriele Columbro <gabriele@apache.org
>> > wrote:
>>> I added opencmis-* in version names, as I suppose other chemistry
>>> hosted projects will follow different release schedule and version
>>> scheme.
>>
>> An alternative is to create new Jira projects like CMISPHP for
>> codebases that follow a separate release schedule. Many of the Jira
>> reports assume that a single Jira project maps to a single release
>> schedule.
>>
>>> 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?
>>
>> The already resolved issues that affect the OpenCMIS codebase should
>> probably be marked as resolved for 0.1.0. This will make the Jira
>> release reports more effective.
>>
>> I'd leave unresolved issues unscheduled unless they're explicitly
>> being targeted for a specific release.
>>
>>> - 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 www.apache.org/dist and the
>>> single
>>> JARs (useful to to application builders) via the standard maven
>>> staging
>>> process.
>>
>> In Jackrabbit we use an assembly and some custom Ant tasks to stage
>> the release artifacts targeted for www.apache.org/dist. See the
>> apache-release profile settings in the Jackrabbit reactor POM [1].
>>
>> [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
>>
>> BR,
>>
>> Jukka Zitting
>
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz
Re: Release 0.1.0-incubating preparation
Posted by David Caruana <da...@alfresco.com>.
There are 68 issues fixed for the components chemistry-abdera, tck and opencmis-*. I'll update their fix version to 0.1.0.
Dave
On 14 Jun 2010, at 09:55, Jukka Zitting wrote:
> Hi,
>
> On Sun, Jun 13, 2010 at 5:27 PM, Gabriele Columbro <ga...@apache.org> wrote:
>> I added opencmis-* in version names, as I suppose other chemistry
>> hosted projects will follow different release schedule and version
>> scheme.
>
> An alternative is to create new Jira projects like CMISPHP for
> codebases that follow a separate release schedule. Many of the Jira
> reports assume that a single Jira project maps to a single release
> schedule.
>
>> 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?
>
> The already resolved issues that affect the OpenCMIS codebase should
> probably be marked as resolved for 0.1.0. This will make the Jira
> release reports more effective.
>
> I'd leave unresolved issues unscheduled unless they're explicitly
> being targeted for a specific release.
>
>> - 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 www.apache.org/dist and the single
>> JARs (useful to to application builders) via the standard maven staging
>> process.
>
> In Jackrabbit we use an assembly and some custom Ant tasks to stage
> the release artifacts targeted for www.apache.org/dist. See the
> apache-release profile settings in the Jackrabbit reactor POM [1].
>
> [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
>
> BR,
>
> Jukka Zitting
Re: Release 0.1.0-incubating preparation
Posted by Florent Guillaume <fg...@nuxeo.com>.
On Mon, Jun 14, 2010 at 1:06 PM, Gabriele Columbro <co...@gmail.com> wrote:
> On Jun 14, 2010, at 10:55 AM, Jukka Zitting wrote:
>> An alternative is to create new Jira projects like CMISPHP for
>> codebases that follow a separate release schedule. Many of the Jira
>> reports assume that a single Jira project maps to a single release
>> schedule.
>
> I also prefer this approach for ease of reporting and separation of
> concerns.
>
> Practically we might need (already):
>
> CMISPHP
> CMISPYTHON
> CMISJS
+1
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Re: Release 0.1.0-incubating preparation
Posted by Gabriele Columbro <co...@gmail.com>.
Hi all,
On Jun 14, 2010, at 10:55 AM, Jukka Zitting wrote:
> Hi,
>
> On Sun, Jun 13, 2010 at 5:27 PM, Gabriele Columbro <gabriele@apache.org
> > wrote:
>> I added opencmis-* in version names, as I suppose other chemistry
>> hosted projects will follow different release schedule and version
>> scheme.
>
> An alternative is to create new Jira projects like CMISPHP for
> codebases that follow a separate release schedule. Many of the Jira
> reports assume that a single Jira project maps to a single release
> schedule.
I also prefer this approach for ease of reporting and separation of
concerns.
Practically we might need (already):
CMISPHP
CMISPYTHON
CMISJS
Am I missing something?
If there's general (lazy) consensus, I will just pick this up with
infrastructure [1] (re-using the current permission model).
>
>> 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?
>
> The already resolved issues that affect the OpenCMIS codebase should
> probably be marked as resolved for 0.1.0. This will make the Jira
> release reports more effective.
>
> I'd leave unresolved issues unscheduled unless they're explicitly
> being targeted for a specific release.
Agreed. I'll check back in 24 hours and see where we stand with it.
>
>> - 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 www.apache.org/dist and the
>> single
>> JARs (useful to to application builders) via the standard maven
>> staging
>> process.
>
> In Jackrabbit we use an assembly and some custom Ant tasks to stage
> the release artifacts targeted for www.apache.org/dist. See the
> apache-release profile settings in the Jackrabbit reactor POM [1].
Thanks Jukka, I'll have a look at it.
Ciao,
Gab
[1] http://www.apache.org/dev/project-creation-tasks.html#tasks
>
> [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
>
> BR,
>
> Jukka Zitting
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz
Re: Release 0.1.0-incubating preparation
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Sun, Jun 13, 2010 at 5:27 PM, Gabriele Columbro <ga...@apache.org> wrote:
> I added opencmis-* in version names, as I suppose other chemistry
> hosted projects will follow different release schedule and version
> scheme.
An alternative is to create new Jira projects like CMISPHP for
codebases that follow a separate release schedule. Many of the Jira
reports assume that a single Jira project maps to a single release
schedule.
> 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?
The already resolved issues that affect the OpenCMIS codebase should
probably be marked as resolved for 0.1.0. This will make the Jira
release reports more effective.
I'd leave unresolved issues unscheduled unless they're explicitly
being targeted for a specific release.
> - 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 www.apache.org/dist and the single
> JARs (useful to to application builders) via the standard maven staging
> process.
In Jackrabbit we use an assembly and some custom Ant tasks to stage
the release artifacts targeted for www.apache.org/dist. See the
apache-release profile settings in the Jackrabbit reactor POM [1].
[1] http://svn.apache.org/repos/asf/jackrabbit/trunk/pom.xml
BR,
Jukka Zitting
RE: Release 0.1.0-incubating preparation
Posted by "Klevenz, Stephan" <st...@sap.com>.
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.
Regards,
Stephan
-----Original Message-----
From: Florian Müller [mailto:fmueller@opentext.com]
Sent: Montag, 14. Juni 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: RE: Release 0.1.0-incubating preparation
Hi,
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
[1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310936&status=1&component=12313420&component=12313421&component=12313419&component=12313422&component=12313424&component=12313423&component=12313425&sorter/field=issuekey&sorter/order=DESC
-----Original Message-----
From: Gabriele Columbro [mailto:gabriele@apache.org]
Sent: Sonntag, 13. Juni 2010 17:27
To: chemistry-dev@incubator.apache.org
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 www.apache.org/dist
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,
ciao!
Gab
[1] https://cwiki.apache.org/CMIS/opencmis-release-documentation.html
[2] https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310936
[3] http://maven.apache.org/developers/release/apache-release.html
[4] http://people.apache.org/~fmui/opencmis/
[5] https://svn.apache.org/repos/asf/incubator/chemistry/opencmis/branches/dev-maven-release
--
Gabriele Columbro
Alfresco Software, Ltd.
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz
RE: Release 0.1.0-incubating preparation
Posted by Florian Müller <fm...@opentext.com>.
Hi,
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
[1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310936&status=1&component=12313420&component=12313421&component=12313419&component=12313422&component=12313424&component=12313423&component=12313425&sorter/field=issuekey&sorter/order=DESC
-----Original Message-----
From: Gabriele Columbro [mailto:gabriele@apache.org]
Sent: Sonntag, 13. Juni 2010 17:27
To: chemistry-dev@incubator.apache.org
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 www.apache.org/dist
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,
ciao!
Gab
[1] https://cwiki.apache.org/CMIS/opencmis-release-documentation.html
[2] https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310936
[3] http://maven.apache.org/developers/release/apache-release.html
[4] http://people.apache.org/~fmui/opencmis/
[5] https://svn.apache.org/repos/asf/incubator/chemistry/opencmis/branches/dev-maven-release
--
Gabriele Columbro
Alfresco Software, Ltd.
Blog: http://www.mindthegab.com
Twitter: http://twitter.com/mindthegabz