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: >>> On 29/03/13 01:48, Gary Martin wrote: >>>> On 28/03/13 20:32, Ryan Ollos wrote: >>>>> On Thu, Mar 28, 2013 at 11:58 AM, Ryan Ollos >>>>> <[email protected]>wrote: >>>>> >>>>>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> On 28.03.2013 07:49, Ryan Ollos wrote: >>>>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <[email protected]> wrote: >>>>>>>> >>>>>>>>> Author: rjollos >>>>>>>>> Date: Thu Mar 28 06:41:58 2013 >>>>>>>>> New Revision: 1648 >>>>>>>>> >>>>>>>>> Log: >>>>>>>>> Releasing Bloodhound 0.5.2 >>>>>>>>> >>>>>>>>> Added: >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz >>>>>>>>> (with props) >>>>>>>>> >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.asc >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.md5 >>>>>>>>> Added: >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz >>>>>>>>> >>>>>>>>> >> ============================================================================== >>>>>>>>> Binary file - no diff available. >>>>>>>>> >>>>>>>>> Propchange: >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz >>>>>>>>> >>>>>>>>> >> ------------------------------------------------------------------------------ >>>>>>>>> svn:mime-type = application/octet-stream >>>>>>>>> >>>>>>>>> Added: >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.asc >> ============================================================================== >>>>>>>>> --- >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.asc >>>>>>>>> (added) >>>>>>>>> +++ >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.asc >>>>>>>>> Thu Mar 28 06:41:58 2013 >>>>>>>>> @@ -0,0 +1,17 @@ >>>>>>>>> +-----BEGIN PGP SIGNATURE----- >>>>>>>>> +Version: GnuPG v1.4.12 (GNU/Linux) >>>>>>>>> + >>>>>>>>> +iQIcBAABAgAGBQJRQvoPAAoJEBkvITON277ikCEP/Am/2SGBCiJGXArySAsVofvY >>>>>>>>> +Il3Z7dyDrq3VByg7S3HMBxGAfIdCE51OcFvFMJlFkEYGgPL3zJq9iYTPWaqaf3R/ >>>>>>>>> +XFecZDYqQ7UPbnA9pwAy2C7rrDwAXT2WTRJxTBIyM0WZzullUF3HouemQJ8Seynt >>>>>>>>> +IEDfO95FBR/yjB4GeBDINdpYi/jYb2Yr/CwtmBgZrFf3euvmgg49amH9G2NnjgDq >>>>>>>>> +5zSVAmHqZvZRQZmXlzj8ONuOjyNgYKm8VXSCpMO6hlMCEk0HZ5QPQokJpqY+U2bH >>>>>>>>> +WEkC6h8iIjIwz5AGOheTBmGW7Ru2MFmPIs57FbzeeSlzknQjymH79kBfW+pIJPXh >>>>>>>>> +zQtavNZbMCkK9TyJQYmE+vow61dT7PRtbTeR1r4AVKRI4Dapqltwmq9hsn6a66Z+ >>>>>>>>> +S90vqWNK9OQCuEJX2ItM4B1b34c7YVJRzpyqkUDn+MLIKzmvaiUDjrusMjY1cLVJ >>>>>>>>> +yMvecckyWhtia3OtB3t4GwEPe4TGr7jbslgp72KE04gtLzjloKs3033r9QFEaJG0 >>>>>>>>> +mivbKfnNbRtImHG12sClxyHT2v4KgfOSMZyc6wcPTN39ivdXgJELC9hTLF/YRrUp >>>>>>>>> +U86FxGYheuUImfErgiccGQHXgU6Khd+bjSHLgIWmYNjdAqz+yqQARKPTG4mAKbeK >>>>>>>>> +r6O8o1lcqGf6FHUAzSJ3 >>>>>>>>> +=c3pg >>>>>>>>> +-----END PGP SIGNATURE----- >>>>>>>>> >>>>>>>>> Added: >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.md5 >> ============================================================================== >>>>>>>>> --- >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.md5 >>>>>>>>> (added) >>>>>>>>> +++ >>>>>>>>> >> release/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz.md5 >>>>>>>>> Thu Mar 28 06:41:58 2013 >>>>>>>>> @@ -0,0 +1,2 @@ >>>>>>>>> +apache-bloodhound-incubating-0.5.2.tar.gz: >>>>>>>>> +56 2F 40 BA E6 14 A9 BD 97 24 07 04 67 2D C6 8A >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> I had meant to do this step last evening but somehow forgot, so I'll >>>>>>> wait a >>>>>>>> few more hours before sending the release announcement, to give the >>>>>>> mirrors >>>>>>>> a chance to update. >>>>>>>> >>>>>>>> I wonder though, if we should make a directory at >>>>>>>> `release/bloodhound` >>>>>>> and >>>>>>>> push the release there instead of or in addition to >>>>>>>> `release/incubator/bloodhound`? >>>>>>> Ah, did I forget to say that? Indeed, this is not an incubator >>>>>>> release; >>>>>>> we need our own release directory. "svn mv" will do what you need. >>>>>>> >>>>>> Ah, I should have mentioned before, that I tried to do the move, >>>>>> but it >>>>>> failed. It looks like I don't have permissions to create the directory >>>>>> directly under "release". I tried again just now: >>>>>> >>>>>> $ svn mv >>>>>> https://dist.apache.org/repos/dist/release/incubator/bloodhound >>>>>> https://dist.apache.org/repos/dist/release/ >>>>>> svn: access to '/repos/dist/!svn/ver/1648/release' forbidden >>>>>> >>>>>> Who has the permissions to do this move operation? I suppose this >>>>>> might >>>>>> need to get sorted out in the infra ticket that Gary is raising. >>>>>> >>>>>> >>>>> For the moment, I'm holding off sending the release announcement >>>>> since we >>>>> wouldn't want it to point to a file that has been relocated. There >>>>> are a >>>>> couple of alternatives, such as doing a copy rather than a move and >>>>> leaving >>>>> `release/incubator/bloodhound` for a while, or waiting until the next >>>>> release to do the directory move. I will continue to hold on the >>>>> release >>>>> announcement and wait for the directory move request that Gary has >>>>> raised >>>>> in infra, unless I see a suggestion to proceed in another way. >>>>> >>>> Is there a particular problem with stating that it is possible to >>>> download from >>>> >> http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz >>>> now it is there? >>>> >>>> Cheers, >>>> Gary >>> 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 -- Branko Čibej Director of Subversion | WANdisco | www.wandisco.com
