You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2011/09/12 09:14:32 UTC
M3 - will try to do it now
I think now we are fully ready to release M3. The maven plugin bugs are fixed, the POM is setup to follow the Apache process using maven-release-plugin, and we have ~ 2 dozens of new features waiting to be released (hats off to Dzmitry on all of these things).
Now I'll need to find time to actually assemble the release and start the vote.
Andrus
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
That's quite neat. I'll need to try it. I had worries about executing platform builds on incompatible platforms - do we have all dependencies to run clean/install like that. So I fixed the M3 via search and replace, but I'll add it to release instructions and we'll use it the next time.
Andrus
On Sep 13, 2011, at 11:25 AM, Dzmitry Kazimirchyk wrote:
> On 09/13/2011 09:08 AM, Andrus Adamchik wrote:
>> Yes, the docbook is a special case - it is not yet ready for inclusion, so it is not linked to the main build. The bigger problem is all other modules that are conditionally added via profiles e.g. when building on a certain platform. E.g.:
>>
>> <profile>
>> <id>mac</id>
>> <modules>
>> <module>cayenne-modeler-mac-ext</module>
>> <module>cayenne-modeler-mac</module>
>> </modules>
>> </profile>
>>
>> Andrus
>
> I've probably find workaround for this. For me running release prepare like this:
>
> mvn release:prepare -DpreparationGoals="clean install" -DautoVersionSubmodules=true -Passembly,generic,mac,windows
>
> set correct version for modules defined in selected profiles.
>
> Dzmitry
>
Re: M3 - will try to do it now
Posted by Dzmitry Kazimirchyk <dk...@gmail.com>.
On 09/13/2011 09:08 AM, Andrus Adamchik wrote:
> Yes, the docbook is a special case - it is not yet ready for inclusion, so it is not linked to the main build. The bigger problem is all other modules that are conditionally added via profiles e.g. when building on a certain platform. E.g.:
>
> <profile>
> <id>mac</id>
> <modules>
> <module>cayenne-modeler-mac-ext</module>
> <module>cayenne-modeler-mac</module>
> </modules>
> </profile>
>
> Andrus
I've probably find workaround for this. For me running release prepare
like this:
mvn release:prepare -DpreparationGoals="clean install"
-DautoVersionSubmodules=true -Passembly,generic,mac,windows
set correct version for modules defined in selected profiles.
Dzmitry
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
Yes, the docbook is a special case - it is not yet ready for inclusion, so it is not linked to the main build. The bigger problem is all other modules that are conditionally added via profiles e.g. when building on a certain platform. E.g.:
<profile>
<id>mac</id>
<modules>
<module>cayenne-modeler-mac-ext</module>
<module>cayenne-modeler-mac</module>
</modules>
</profile>
Andrus
On Sep 13, 2011, at 1:02 AM, Richard Frovarp wrote:
> On 09/12/2011 03:26 PM, Andrus Adamchik wrote:
>>
>> On Sep 12, 2011, at 10:42 PM, Andrus Adamchik wrote:
>>
>>>
>>> I am going to document these steps on the site once we finish the release end to end.
>>
>> Ok, there's always a catch... after mvn release:whatever, we have a bunch of POMs still not updated (excluded from the default release profile) :
>>
>> $ find . -name pom.xml |xargs grep SNAPSHOT
>> ./assembly/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./docs/docbook/cayenne-guide/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./docs/docbook/main/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./docs/docbook/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-generic/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-generic-ext/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-mac/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-mac-ext/pom.xml: <version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-win/pom.xml: <version>3.1-SNAPSHOT</version>
>>
>> So will still have to change those with Perl until we figure out a better way. Will continue on this hopefully tomorrow.
>>
>> Andrus
>>
>
> They're being excluded because they don't have a chain from ./pom.xml to them. For instance, docs/pom.xml just references /docs/doc and not docs/docbook under the module declaration.
>
> I don't know if adding them to the module declarations has a side effect you don't want or not.
>
Re: M3 - will try to do it now
Posted by Richard Frovarp <rf...@apache.org>.
On 09/12/2011 03:26 PM, Andrus Adamchik wrote:
>
> On Sep 12, 2011, at 10:42 PM, Andrus Adamchik wrote:
>
>>
>> I am going to document these steps on the site once we finish the release end to end.
>
> Ok, there's always a catch... after mvn release:whatever, we have a bunch of POMs still not updated (excluded from the default release profile) :
>
> $ find . -name pom.xml |xargs grep SNAPSHOT
> ./assembly/pom.xml: <version>3.1-SNAPSHOT</version>
> ./docs/docbook/cayenne-guide/pom.xml: <version>3.1-SNAPSHOT</version>
> ./docs/docbook/main/pom.xml: <version>3.1-SNAPSHOT</version>
> ./docs/docbook/pom.xml: <version>3.1-SNAPSHOT</version>
> ./modeler/cayenne-modeler-generic/pom.xml: <version>3.1-SNAPSHOT</version>
> ./modeler/cayenne-modeler-generic-ext/pom.xml: <version>3.1-SNAPSHOT</version>
> ./modeler/cayenne-modeler-mac/pom.xml: <version>3.1-SNAPSHOT</version>
> ./modeler/cayenne-modeler-mac-ext/pom.xml: <version>3.1-SNAPSHOT</version>
> ./modeler/cayenne-modeler-win/pom.xml: <version>3.1-SNAPSHOT</version>
>
> So will still have to change those with Perl until we figure out a better way. Will continue on this hopefully tomorrow.
>
> Andrus
>
They're being excluded because they don't have a chain from ./pom.xml to
them. For instance, docs/pom.xml just references /docs/doc and not
docs/docbook under the module declaration.
I don't know if adding them to the module declarations has a side effect
you don't want or not.
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Sep 12, 2011, at 10:42 PM, Andrus Adamchik wrote:
>
> I am going to document these steps on the site once we finish the release end to end.
Ok, there's always a catch... after mvn release:whatever, we have a bunch of POMs still not updated (excluded from the default release profile) :
$ find . -name pom.xml |xargs grep SNAPSHOT
./assembly/pom.xml: <version>3.1-SNAPSHOT</version>
./docs/docbook/cayenne-guide/pom.xml: <version>3.1-SNAPSHOT</version>
./docs/docbook/main/pom.xml: <version>3.1-SNAPSHOT</version>
./docs/docbook/pom.xml: <version>3.1-SNAPSHOT</version>
./modeler/cayenne-modeler-generic/pom.xml: <version>3.1-SNAPSHOT</version>
./modeler/cayenne-modeler-generic-ext/pom.xml: <version>3.1-SNAPSHOT</version>
./modeler/cayenne-modeler-mac/pom.xml: <version>3.1-SNAPSHOT</version>
./modeler/cayenne-modeler-mac-ext/pom.xml: <version>3.1-SNAPSHOT</version>
./modeler/cayenne-modeler-win/pom.xml: <version>3.1-SNAPSHOT</version>
So will still have to change those with Perl until we figure out a better way. Will continue on this hopefully tomorrow.
Andrus
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
Progress report... So this approximate sequence of steps based on http://www.apache.org/dev/publishing-maven-artifacts.html , but with our current POM works to create a staging release repo that we can use for Maven testing
1. Make sure "apache-releases" repository is configured in ~/.m2/settings.xml and an appropriate password is setup.
2. Need to do Subversion checkout.. git-svn checkout won't work.
3. Release commands:
mvn release:clean
mvn release:prepare -DautoVersionSubmodules=true
Here running into something described in the docs: "Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and ' svn: No such revision X '. Wait 10 seconds and run mvn release:prepare again." Well this is not a joke. It fails indeed, and requires a re-run.
mvn release:perform -P gpg [-Dgpg.keyname=B8AF90BF]
4. "Close" the staging repo:
4.1 Login to https://repository.apache.org/ with Apache ID/password.
4.2 Go to Staging Repositories page.
4.3 Select a staging repository you just created.
4.4 Click Close
After these steps we have a neat staging repository containing Cayenne 3.1M3: https://repository.apache.org/content/repositories/orgapachecayenne-052/ ready to be used for testing. I'd specifically request release-testing volunteers to check that the Maven plugins work. E.g. in M2 cgen couldn't pull all its dependencies. That should be fixed. Not sure about the Modeler plugin, but worth trying it too (though IMO this won't be a release showstopper either way).
Other than the above, downloadable assemblies process is teh same as before, and I am moving to that now.
I am going to document these steps on the site once we finish the release end to end.
Andrus
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
Ari,
Since I have a bit of time right now, I guess I'll proceed with preparing the release. But I don't want it look like I am pushing it through when there are still unresolved concerns. So if we want to cancel it for this or some other reason, let's resume this discussion.
Andrus
On Sep 12, 2011, at 3:40 PM, Andrus Adamchik wrote:
> I suggest CAY-1210 goes in after M3. It has a potential of introducing lots of regression issues and will require some effort to setup the unit tests. So my vote is to go ahead with M3 (which is long overdue) and commit CAY-1210 to trunk once the release is tagged, so that we can test it at a slower pace.
>
> Andrus
>
>
>
> On Sep 12, 2011, at 3:16 PM, Aristedes Maniatis wrote:
>
>> On 12/09/11 5:14 PM, Andrus Adamchik wrote:
>>> I think now we are fully ready to release M3. The maven plugin bugs are fixed, the POM is setup to follow the Apache process using maven-release-plugin, and we have ~ 2 dozens of new features waiting to be released (hats off to Dzmitry on all of these things).
>>>
>>> Now I'll need to find time to actually assemble the release and start the vote.
>>>
>>> Andrus
>>
>> If we could get CAY-1210 into this M3 build I'll do some testing. Do you want to merge the code or should I?
>>
>> Ari
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
>
>
Re: M3 - will try to do it now
Posted by Andrus Adamchik <an...@objectstyle.org>.
I suggest CAY-1210 goes in after M3. It has a potential of introducing lots of regression issues and will require some effort to setup the unit tests. So my vote is to go ahead with M3 (which is long overdue) and commit CAY-1210 to trunk once the release is tagged, so that we can test it at a slower pace.
Andrus
On Sep 12, 2011, at 3:16 PM, Aristedes Maniatis wrote:
> On 12/09/11 5:14 PM, Andrus Adamchik wrote:
>> I think now we are fully ready to release M3. The maven plugin bugs are fixed, the POM is setup to follow the Apache process using maven-release-plugin, and we have ~ 2 dozens of new features waiting to be released (hats off to Dzmitry on all of these things).
>>
>> Now I'll need to find time to actually assemble the release and start the vote.
>>
>> Andrus
>
> If we could get CAY-1210 into this M3 build I'll do some testing. Do you want to merge the code or should I?
>
> Ari
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: M3 - will try to do it now
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 12/09/11 5:14 PM, Andrus Adamchik wrote:
> I think now we are fully ready to release M3. The maven plugin bugs are fixed, the POM is setup to follow the Apache process using maven-release-plugin, and we have ~ 2 dozens of new features waiting to be released (hats off to Dzmitry on all of these things).
>
> Now I'll need to find time to actually assemble the release and start the vote.
>
> Andrus
If we could get CAY-1210 into this M3 build I'll do some testing. Do you want to merge the code or should I?
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A