[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010043#comment-14010043
]
Andrew Bayer edited comment on JCLOUDS-576 at 5/27/14 6:51 PM:
---------------------------------------------------------------
So I'm fiddling around with ways of dealing with the stupid snapshots crap -
what I've got so far is the following:
Before running release:prepare in one of the other repos, do the following:
- mvn versions:update-parent
- mvn versions:update-properties -DincludeProperties=jclouds.version
- mvn versions:use-releases -Dincludes=org.apache.jclouds*:*
- git add, git commit, etc
And then after the release:perform, make some changes to the commit that
switches to the next snapshot version (after you've mvn install'd the new
SNAPSHOT versions of all the dependencies of this repo):
- mvn versions:update-parent -DallowSnapshots=true
-DparentVersion="[1.7.4-SNAPSHOT]"
- mvn versions:update-properties -DincludeProperties=jclouds.version
- mvn versions:use-next-snapshots -DallowSnapshots=true
-Dincludes=org.apache.jclouds*:*
- git add, git commit --amend (to edit the existing commit)
I think. Will experiment more.
EDIT: Some more experimentation done - updated accordingly. Assuming this all
works in the end, I think we can automate this via the release plugin.
was (Author: abayer):
So I'm fiddling around with ways of dealing with the stupid snapshots crap -
what I've got so far is the following:
Before running release:prepare in one of the other repos, do the following:
- mvn versions:update-parent
- mvn versions:use-releases -Dincludes=org.apache.jclouds*:*
- git add, git commit, etc
And then after the release:perform, make some changes to the commit that
switches to the next snapshot version (after you've mvn install'd the new
SNAPSHOT versions of all the dependencies of this repo):
- mvn versions:update-parent -DallowSnapshots=true
-DparentVersion="[1.7.4-SNAPSHOT]"
- mvn versions:use-next-snapshots -DallowSnapshots=true
-Dincludes=org.apache.jclouds*:*
- git add, git commit --amend (to edit the existing commit)
I think. Will experiment more.
EDIT: Some more experimentation done - updated accordingly. Assuming this all
works in the end, I think we can automate this via the release plugin.
> Automate releases
> -----------------
>
> Key: JCLOUDS-576
> URL: https://issues.apache.org/jira/browse/JCLOUDS-576
> Project: jclouds
> Issue Type: Improvement
> Reporter: Everett Toews
>
> I am emotionally scarred by trying to release jclouds. The release process is
> sort of documented in [Releasing
> jclouds|https://wiki.apache.org/jclouds/Releasing%20jclouds]. It's a 17 step
> process that has a lot of assumptions baked into it. There is a lot of manual
> steps and manual data entry that are all very error prone. It's also very
> time consuming.
> These problems are compounded by the fact that we have so many repos. Whether
> or not we bring the repos back together we need to work towards automating
> the release process. Performing a release should be a trivial thing to do.
> This isn't going to happen all at once. We need to take steps to get there.
> Here's what I propose as the first steps.
> # Change the release:prepare step so that it isn't interactive and require
> you to manually enter info to resolve the dependencies.
> # Automate the release of the jclouds main repo. This probably means a
> script with the steps in [Releasing
> jclouds|https://wiki.apache.org/jclouds/Releasing%20jclouds] coded into it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
