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 <n...@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 <n...@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 <andrew.ba...@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 <andr...@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 >>>>
