On Mar 29, 2013 5:25 AM, "Gary Martin" <[email protected]> wrote: > > On 29/03/13 11:32, Gary Martin wrote: >> >> On 29/03/13 10:22, Gary Martin wrote: >>> >>> On 29/03/13 09:10, Branko Čibej wrote: >>>> >>>> On 29.03.2013 08:01, Ryan Ollos wrote: >>>>> >>>>> On Thu, Mar 28, 2013 at 10:59 PM, Branko Čibej <[email protected]> wrote: >>>>> >>>>>> On 29.03.2013 03:14, Gary Martin wrote: >>>>>>> >>>>>>> It does look like infra should be involved in the migration so I >>>>>>> raised https://issues.apache.org/jira/browse/INFRA-6083 to make sure >>>>>>> that the automated release and archiving works. >>>>>> >>>>>> Inappropriate; the incubating releases have to stay where they are. >>>>>> >>>>> Ah, it's a good thing I was blocked from doing an `svn mv` then, because I >>>>> had tried to move the entire `bloodhound` directory. >>>>> >>>>> >>>>>>> However, as I tried to imply above, I don't think we need to wait for >>>>>>> this to complete before announcing the release. >>>>>> >>>>>> There's no "I think" about it; we should follow this process: >>>>>> >>>>>> http://www.apache.org/dev/release-publishing.html#distribution >>>>>> >>>>>> which clearly states that our release bits should be in >>>>>> >>>>>> https://dist.apache.org/repos/dist/release/bloodhound >>>>>> >>>>>> All PMC members have access to this directory, the only problem is that >>>>>> it doesn't exist yet. As I said, I believe you as PMC chair should have >>>>>> access to create the directory, so try >>>>>> >>>>>> svn mkdir https://dist.apache.org/repos/dist/release/bloodhound >>>>>> >>>>>> and if that doesn't work, ask Infra to create the directory. >>>>>> >>>>>> -- Brane >>>>>> >>>>> If I'm reading that page correctly, then we will need to remove the >>>>> previous release from >>>>> https://dist.apache.org/repos/dist/release/bloodhoundwhen we release >>>>> publish a new release (which is obviously not applicable >>>>> for our first release). >>>> >>>> There are instructions for archiving old releases there, too. I don't >>>> think they apply to incubating releases, but perhaps they do, dunno. >>>> >>>> >>>>> As an incubator project, we've left all of our releases in >>>>> https://dist.apache.org/repos/dist/release/incubator/bloodhound. >>>>> >>>>> Anyway, if what I've said is correct, I'll add a step in our release >>>>> process to cover removal of the old release when the new release is >>>>> published. >>>> >>>> +1 >>>> >>> >>> OK, whatever the case is I do not have the permissions to create the directory so I have updated the ticket noting that I made the attempt. At the moment I am expecting that ticket to result in whatever the right thing turns out to be. >>> >>> Cheers, >>> Gary >> >> >> Right, the https://dist.apache.org/repos/dist/release/incubator/bloodhound and https://dist.apache.org/repos/dist/release/incubator/bloodhound have been created for us (thanks Gavin). So, we should be ready to finish this release. >> >> Ryan: are you happy to finish off the process again? I'll clean up the old incubator/bloodhound directories once that is done. >> >> Cheers, >> Gary > > > I have just updated the https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess wiki page to remove all incubation related parts and correct all the various paths. > > Being close to release, it is probably worth checking that I haven't done anything stupid with the release [ANNOUNCE] email. > > Cheers, > Gary
I commited the files a few hours back, and just wanted to mention here since there wasn't a notification email. I'll send the release announcement in a few hours after giving the mirrors time to update.
