Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

Hi!

@abayer won't have a decent Internet connection to run the release
this weekend and I'm taking it. Consider the 1.9.x branch frozen!
I expect the first RC to be released tonight/tomorrow.

I.

On 31 July 2015 at 08:27, Andrew Bayer <an...@gmail.com> wrote:
> That's what it sounds like to me, which is...odd. I'll poke around.
>
> A.
>
> On Thu, Jul 30, 2015 at 11:02 PM, Andrew Phillips <an...@apache.org>
> wrote:
>
>> what's happening with https://gist.github.com/abayer/290424448caf1e1cca74?
>>>
>>
>> Any idea what this character is?
>>
>> /src/main\300java
>>>
>>
>> I guess that's meant to be a "normal" slash? Something to do with Git
>> encoding settings, perhaps?
>>
>> Regards
>>
>> ap
>>

Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

Finally we have jclouds-1.9.1-rc1!

The last version of the release script worked fine. As it now clones
all the repos to always start from a clean state, I've changed it to
also push the generated tags, as there is (shouldn't be :D) no chance
that unexpected files are there.

Preparing the release is now just about running one command, closing
the staging repo and copy/pasting links to the vote thread (the
release script already outputs the URL and hashes for all tags to make
that easier).

Let's see if everything is OK and we don't need a RC2! :)

Please, participate, test the release, run the live tests and share
the results in the DISCUSS thread.

Thanks to everyone that helped!

I.

On 2 August 2015 at 11:46, Ignasi Barrera <na...@apache.org> wrote:
> Just for the record, and regarding the gist, I found the same issue
> 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.
>
> I haven't found a place in the release script that could generate
> that, but I'm trying now with a modified/improved version and see what
> I find.
>
> On 1 August 2015 at 22:51, Ignasi Barrera <na...@apache.org> wrote:
>> Hi!
>>
>> @abayer won't have a decent Internet connection to run the release
>> this weekend and I'm taking it. Consider the 1.9.x branch frozen!
>> I expect the first RC to be released tonight/tomorrow.
>>
>> I.
>>
>> On 31 July 2015 at 08:27, Andrew Bayer <an...@gmail.com> wrote:
>>> That's what it sounds like to me, which is...odd. I'll poke around.
>>>
>>> A.
>>>
>>> On Thu, Jul 30, 2015 at 11:02 PM, Andrew Phillips <an...@apache.org>
>>> wrote:
>>>
>>>> what's happening with https://gist.github.com/abayer/290424448caf1e1cca74?
>>>>>
>>>>
>>>> Any idea what this character is?
>>>>
>>>> /src/main\300java
>>>>>
>>>>
>>>> I guess that's meant to be a "normal" slash? Something to do with Git
>>>> encoding settings, perhaps?
>>>>
>>>> Regards
>>>>
>>>> ap
>>>>

Re: 1.9.1 - what's left?

[Andrew Phillips <an...@apache.org>]

> 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.

Many thanks for making this happen, Ignasi and everyone who tested!

ap

Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

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 <za...@rackspace.com> wrote:
> Great job!
> ________________________________________
> From: Andrew Bayer <an...@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 <na...@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 <an...@gmail.com> wrote:
>> > Thanks guys for your great effort!
>> >
>> > On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <na...@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
>> >>
>>

Re: 1.9.1 - what's left?

[Zack Shoylev <za...@RACKSPACE.COM>]

Great job!
________________________________________
From: Andrew Bayer <an...@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 <na...@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 <an...@gmail.com> wrote:
> > Thanks guys for your great effort!
> >
> > On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <na...@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
> >>
>

Re: 1.9.1 - what's left?

[Andrew Bayer <an...@gmail.com>]

Thanks for driving this, Ignasi!

A.

On Thu, Aug 6, 2015 at 9:04 PM, Ignasi Barrera <na...@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 <an...@gmail.com> wrote:
> > Thanks guys for your great effort!
> >
> > On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <na...@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
> >>
>

Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

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 <an...@gmail.com> wrote:
> Thanks guys for your great effort!
>
> On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <na...@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
>>

Re: 1.9.1 - what's left?

[Andrea Turli <an...@gmail.com>]

Thanks guys for your great effort!

On Sun, Aug 2, 2015 at 7:53 PM Ignasi Barrera <na...@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
>

Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

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

Re: 1.9.1 - what's left?

[Andrew Phillips <an...@apache.org>]

> 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

Re: 1.9.1 - what's left?

[Ignasi Barrera <na...@apache.org>]

Just for the record, and regarding the gist, I found the same issue
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.

I haven't found a place in the release script that could generate
that, but I'm trying now with a modified/improved version and see what
I find.

On 1 August 2015 at 22:51, Ignasi Barrera <na...@apache.org> wrote:
> Hi!
>
> @abayer won't have a decent Internet connection to run the release
> this weekend and I'm taking it. Consider the 1.9.x branch frozen!
> I expect the first RC to be released tonight/tomorrow.
>
> I.
>
> On 31 July 2015 at 08:27, Andrew Bayer <an...@gmail.com> wrote:
>> That's what it sounds like to me, which is...odd. I'll poke around.
>>
>> A.
>>
>> On Thu, Jul 30, 2015 at 11:02 PM, Andrew Phillips <an...@apache.org>
>> wrote:
>>
>>> what's happening with https://gist.github.com/abayer/290424448caf1e1cca74?
>>>>
>>>
>>> Any idea what this character is?
>>>
>>> /src/main\300java
>>>>
>>>
>>> I guess that's meant to be a "normal" slash? Something to do with Git
>>> encoding settings, perhaps?
>>>
>>> Regards
>>>
>>> ap
>>>