The release notes PR is here: https://github.com/jclouds/jclouds-site/pull/170
Feel free to edit it and push directly to the branch!

On 6 August 2015 at 21:16, Zack Shoylev <zack.shoy...@rackspace.com> wrote:
> Great job!
> ________________________________________
> From: Andrew Bayer <andrew.ba...@gmail.com>
> Sent: Thursday, August 6, 2015 2:09 PM
> To: dev@jclouds.apache.org
> Subject: Re: 1.9.1 - what's left?
>
> Thanks for driving this, Ignasi!
>
> A.
>
> On Thu, Aug 6, 2015 at 9:04 PM, Ignasi Barrera <n...@apache.org> wrote:
>
>> The release has been made. We're waiting for the release files to be
>> replicated to the mirrors and the artifacts to reach Maven Central to
>> send the official announcement.
>>
>> I'll also open a PR to add the release notes to the site and push the
>> branch to the ASF repo so everyone can contribute directly to it.
>>
>> Although we've not planned another 1.9.x release, the 1.9.x branch is
>> open again.
>>
>> Cheers!
>>
>> I.
>>
>> On 3 August 2015 at 10:12, Andrea Turli <andrea.tu...@gmail.com> wrote:
>> > Thanks guys for your great effort!
>> >
>> > On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <n...@apache.org> wrote:
>> >
>> >> I don't think we have corrupted files in the repo; jenkins would
>> complain.
>> >>
>> >> One failure I got was in jclouds-labs detecting the digitalocean2
>> folder as
>> >> deleted and modified, and in another build the same happened in
>> >> karaf/commands (this time labs suceeded). It seems to appear at random
>> due
>> >> to some git weirdness in the local checkout.
>> >>
>> >> I haven't been able to consistently reproduce the issue so I can't say
>> >> where the problem is/was.
>> >>
>> >> For anyone interested in testing the release script, you can find it
>> here
>> >> [1] (it has been created in OSX so it might need some fixes to make it
>> 100%
>> >> linux friendly). Take care to comment out the "mvn deploy" and the "git
>> >> push" steps at the end of the script to avoid uploading the artifacts
>> to a
>> >> staging repo and to avoid pushing a new RC.
>> >>
>> >> I.
>> >>
>> >> [1] https://dist.apache.org/repos/dist/dev/jclouds/prepare_release.sh
>> >>
>> >> > but at different (and random) repos. It appears when Git has a
>> >> > corrupted file or there are changes in a file (the pom.xml with the
>> >> > updated version), but the file is also marked to be deleted.
>> >> >
>> >>
>> >> Glad to hear things seem to have worked this time around - do you think
>> the
>> >> error was caused by an issue in the script, or do you suspect we have
>> some
>> >> corrupt files in one or the repos?
>> >>
>> >> Many thanks for getting the RC out - trying to verify it now ;-)
>> >>
>> >> Regards
>> >>
>> >> ap
>> >>
>>

Reply via email to