jclouds-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Bayer <andrew.ba...@gmail.com>
Subject Re: Apache jclouds 1.6.1-incubating RC0 is ready for review
Date Wed, 29 May 2013 19:39:55 GMT
For 1.6.1-incubating, at least, no, that's probably sufficient. I just
don't know what needs to be done to get it in the right format for the site
etc.

A.

On Wed, May 29, 2013 at 4:19 AM, Everett Toews
<everett.toews@rackspace.com>wrote:

> Do we need something more than the Edit/Copy Release Notes HTML section of
> the release notes [1]?
>
> Everett
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>
> On May 28, 2013, at 6:06 PM, Andrew Bayer wrote:
>
> Sounds good - I'll open a JIRA for figuring out a way to autogenerate them,
> or at least to autogenerate a starting point, 'cos that'd be nice. =)
>
> A.
>
> On Tue, May 28, 2013 at 2:49 PM, Becca Wood <silkysun@apache.org<mailto:
> silkysun@apache.org>> wrote:
>
> I don't know of a way to auto generate release notes, but I'll be happy to
> read through the commit history and draft a copy.  Sound good?
>
>
> On Tue, May 28, 2013 at 2:41 PM, Andrew Bayer <andrew.bayer@gmail.com
> <mailto:andrew.bayer@gmail.com>
> wrote:
>
> fwiw, here are the list of JIRAs changed in this release:
>
>
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>
> A.
>
>
> On Tue, May 28, 2013 at 2:22 PM, Andrew Bayer <andrew.bayer@gmail.com
> <mailto:andrew.bayer@gmail.com>
> wrote:
>
> Oh crap, I forgot one key part - the release notes. silkysun, how do we
> generate those?
>
> A.
>
>
> On Tue, May 28, 2013 at 2:21 PM, Andrew Bayer <andrew.bayer@gmail.com
> <mailto:andrew.bayer@gmail.com>
> wrote:
>
> Note - this is *not* an official vote thread, hence it not also going
> to
> incubator@. This is an informal preliminary to the official release
> vote.
>
> I've cut the first attempt at a viable RC for 1.6.1-incubating. The
> bits
> we'll end up voting on are in
>
> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-0/-notethat the binary
artifacts are only there for the CLI, since we don't
> have binary tarballs for any other projects. And remember that you're
> not
> actually voting on the binary artifacts anyway - you're voting on the
> *source*.
>
> I've pushed the "*-1.6.1-incubating-rc0" tags in the appropriate git
> repos, though I have *not* pushed HEAD on 1.6.x from my local repos as
> of
> yet - that's because my local 1.6.x branches have the commits updating
> the
> versions to 1.6.1-incubating and then onward to 1.6.2-SNAPSHOT, and an
> additional commit in the case of all the ones but jclouds proper
> bumping up
> the jclouds (and other project) dependencies to 1.6.1-incubating.
> Those'll
> get pushed when the release has actually passed the Incubator PMC vote
> and
> we are actually releasing - otherwise, we're in for a hellish time
> dealing
> with undoing the changes to put any additional fixes in, due to the
> fact
> that we can't force-push to ASF's git repos.
>
> So what do you all need to do in order to validate the RC? Take a look
> at the "Validating the release" section at
> http://helix.incubator.apache.org/releasing.html for an idea (though
> note that we don't need -Prat in a mvn call - we always call the rat
> plugin). Remember that you can get the KEYS file from
> http://www.apache.org/dist/incubator/jclouds/KEYS. Beyond the
> source/signature/license/etc validation (which is what is going to
> matter
> to the IPMC), we care whether the code actually *works*. So please
> give the
> bits a shot in any apps you've got depending on jclouds, run the live
> tests
> for any providers you have creds for, etc.
>
> Again, this isn't a formal vote, so there isn't a formal deadline for
> getting your response in. But the sooner you can, the sooner I can get
> the
> bits in front of the IPMC for the formal vote process. So I'm going to
> give
> it 'til sometime on Thursday, and if I haven't heard of any problems by
> then, I'll kick off the formal release vote then. The
> bits/repos/tags/etc
> are below. Thanks!
>
> - jclouds
>     - Maven staging repo -
>
> https://repository.apache.org/content/repositories/orgapachejclouds-015/
>     - tag - jclouds-1.6.1-incubating-rc0
>     - source artifact -
> jclouds-multi-1.6.1-incubating-source-release.tar.gz
>
> - chef
>     - Maven staging repo -
>
> https://repository.apache.org/content/repositories/orgapachejclouds-021/
>     - tag - jclouds-chef-1.6.1-incubating-rc0
>     - source artifact -
> chef-project-1.6.1-incubating-source-release.tar.gz
>
> - labs
>     - Maven staging repo -
>
> https://repository.apache.org/content/repositories/orgapachejclouds-020/
>     - tag - jclouds-labs-1.6.1-incubating-rc0
>     - source artifact -
> jclouds-labs-1.6.1-incubating-source-release.tar.gz
>
> - karaf
>     - Maven staging repo -
>
> https://repository.apache.org/content/repositories/orgapachejclouds-022/
>     - tag - jclouds-karaf-1.6.1-incubating-rc0
>     - source artifact -
> jclouds-karaf-pom-1.6.1-incubating-source-release.tar.gz
>
> - cli
>     - Maven staging repo -
>
> https://repository.apache.org/content/repositories/orgapachejclouds-023/
>     - tag - jclouds-cli-1.6.1-incubating-rc0
>     - source artifact -
> jclouds-cli-pom-1.6.1-incubating-source-release.tar.gz
>     - binary artifacts - jclouds-cli-1.6.1-incubating.tar.gz,
> jclouds-cli-1.6.1-incubating.zip
>
> A.
>
>
>
>
>
>
>

Mime
View raw message