[
https://issues.apache.org/jira/browse/JCLOUDS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010091#comment-14010091
]
Andrew Bayer edited comment on JCLOUDS-576 at 5/27/14 6:55 PM:
---------------------------------------------------------------
Ah, and we'll need to work in the property updating somehow - will play with
the versions:update-properties goal...
EDIT: Well, I'm pretty confident in how that works for going from release to
SNAPSHOT, so added that. =)
was (Author: abayer):
Ah, and we'll need to work in the property updating somehow - will play with
the versions:update-properties goal...
> 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)
