You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Ryan Ollos <ry...@wandisco.com> on 2013/03/28 07:49:33 UTC
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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`?
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Joe Dreimann <jo...@wandisco.com>.
When I first added this my intention was to show progress on the front page, instead of the same static information. Everything apart from the latest version was collapsed (with forward slashes to separate items).
I still believe progress/activity should be immediately visible from the page most people land on.
I have now removed information of release 0.1 & 0.2 and changed the style of the 0.5.1 and 0.5.2 releases since they're arguably minor. That should deal with it for now.
Cheers,
Joe
________________________
@jdreimann - Twitter
Sent from my phone
On 1 Apr 2013, at 11:19, Gary Martin <ga...@wandisco.com> wrote:
> On 01/04/13 11:15, Andrej Golcov wrote:
>> Change log section on BH root page [1] is quite long now. It hides
>> main features description. I suggest to move change log to a separate
>> page or show the last release notes with possibility to read more.
>> What do you think?
>>
>> [1] https://issues.apache.org/bloodhound
>>
>> Cheers, Andrej
>
> I agree although I would probably just leave the front page with a link to the changelog page.
>
> Cheers,
> Gary
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
On 01/04/13 11:15, Andrej Golcov wrote:
> Change log section on BH root page [1] is quite long now. It hides
> main features description. I suggest to move change log to a separate
> page or show the last release notes with possibility to read more.
> What do you think?
>
> [1] https://issues.apache.org/bloodhound
>
> Cheers, Andrej
I agree although I would probably just leave the front page with a link
to the changelog page.
Cheers,
Gary
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Andrej Golcov <an...@digiverse.si>.
Change log section on BH root page [1] is quite long now. It hides
main features description. I suggest to move change log to a separate
page or show the last release notes with possibility to read more.
What do you think?
[1] https://issues.apache.org/bloodhound
Cheers, Andrej
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Sat, Mar 30, 2013 at 6:26 AM, Gary Martin <ga...@wandisco.com>wrote:
> On 29/03/13 18:16, Ryan Ollos wrote:
>
>> 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.
>>
>
> I suspect that it not everything will be set up yet. The last I looked,
> https://issues.apache.org/**jira/browse/INFRA-6083<https://issues.apache.org/jira/browse/INFRA-6083>suggested that the locations are available but nothing more. That suggests
> we still have to wait for update notification emails and the publishing. By
> the looks of it, the rest of the work is expected to happen within the next
> three days.
>
> Cheers,
> Gary
>
I just realized that although
https://dist.apache.org/repos/dist/release/bloodhound/ is a valid link to
the release package, the URLs on
http://www.apache.org/dyn/closer.cgi/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gzdo
not point to the release package. This is bad since the latter is the
URL I used in the release announcement. I didn't realize the
"dyn/closer.cgi" page might show download links for non-existent downloads,
and didn't check things carefully enough before sending the announcement.
After we sort that out I may need to update site/index.html and WikiStart
again.
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
On 29/03/13 18:16, Ryan Ollos wrote:
> 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.
I suspect that it not everything will be set up yet. The last I looked,
https://issues.apache.org/jira/browse/INFRA-6083 suggested that the
locations are available but nothing more. That suggests we still have to
wait for update notification emails and the publishing. By the looks of
it, the rest of the work is expected to happen within the next three days.
Cheers,
Gary
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mar 29, 2013 5:25 AM, "Gary Martin" <ga...@wandisco.com> 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 <br...@wandisco.com>
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.
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
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 <br...@wandisco.com>
>>>> 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
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
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 <br...@wandisco.com>
>>> 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
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
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 <br...@wandisco.com> 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
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Branko Čibej <br...@wandisco.com>.
On 29.03.2013 08:01, Ryan Ollos wrote:
> On Thu, Mar 28, 2013 at 10:59 PM, Branko Čibej <br...@wandisco.com> 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
>>>>> <ry...@wandisco.com>wrote:
>>>>>
>>>>>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej
>>>>>> <br...@wandisco.com>wrote:
>>>>>>
>>>>>>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>>>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, Mar 28, 2013 at 10:59 PM, Branko Čibej <br...@wandisco.com> 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
> >>> <ry...@wandisco.com>wrote:
> >>>
> >>>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej
> >>>> <br...@wandisco.com>wrote:
> >>>>
> >>>>> On 28.03.2013 07:49, Ryan Ollos wrote:
> >>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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).
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.
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Branko Čibej <br...@wandisco.com>.
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
>>> <ry...@wandisco.com>wrote:
>>>
>>>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej
>>>> <br...@wandisco.com>wrote:
>>>>
>>>>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
> 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
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
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
>> <ry...@wandisco.com>wrote:
>>
>>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej
>>> <br...@wandisco.com>wrote:
>>>
>>>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
However, as I tried to imply above, I don't think we need to wait for
this to complete before announcing the release.
Cheers,
Gary
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, Mar 28, 2013 at 6:48 PM, Gary Martin <ga...@wandisco.com>wrote:
> On 28/03/13 20:32, Ryan Ollos wrote:
>
>> On Thu, Mar 28, 2013 at 11:58 AM, Ryan Ollos <ry...@wandisco.com>**
>> wrote:
>>
>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej <brane@wandisco.com
>>> >wrote:
>>>
>>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>>>
>>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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)
>>>>>> +
>>>>>> +**iQIcBAABAgAGBQJRQvoPAAoJEBkvIT**ON277ikCEP/Am/**
>>>>>> 2SGBCiJGXArySAsVofvY
>>>>>> +**Il3Z7dyDrq3VByg7S3HMBxGAfIdCE5**1OcFvFMJlFkEYGgPL3zJq9iYTPWaqa**
>>>>>> f3R/
>>>>>> +**XFecZDYqQ7UPbnA9pwAy2C7rrDwAXT**2WTRJxTBIyM0WZzullUF3HouemQJ8S**
>>>>>> eynt
>>>>>> +IEDfO95FBR/yjB4GeBDINdpYi/**jYb2Yr/**CwtmBgZrFf3euvmgg49amH9G2NnjgD*
>>>>>> *q
>>>>>> +**5zSVAmHqZvZRQZmXlzj8ONuOjyNgYK**m8VXSCpMO6hlMCEk0HZ5QPQokJpqY+**
>>>>>> U2bH
>>>>>> +**WEkC6h8iIjIwz5AGOheTBmGW7Ru2MF**mPIs57FbzeeSlzknQjymH79kBfW+**
>>>>>> pIJPXh
>>>>>> +zQtavNZbMCkK9TyJQYmE+**vow61dT7PRtbTeR1r4AVKRI4Dapqlt**wmq9hsn6a66Z+
>>>>>> +**S90vqWNK9OQCuEJX2ItM4B1b34c7YV**JRzpyqkUDn+**
>>>>>> MLIKzmvaiUDjrusMjY1cLVJ
>>>>>> +**yMvecckyWhtia3OtB3t4GwEPe4TGr7**jbslgp72KE04gtLzjloKs3033r9QFE**
>>>>>> aJG0
>>>>>> +**mivbKfnNbRtImHG12sClxyHT2v4Kgf**OSMZyc6wcPTN39ivdXgJELC9hTLF/**
>>>>>> 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/incubator/bloodhound>
>>> https://dist.apache.org/repos/**dist/release/<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<http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.5.2.tar.gz>now it is there?
>
> Cheers,
> Gary
>
I don't think there will be a problem as long as the file isn't moved as
part of our directory reorganization after graduation.
Why not just move the directory though?
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
On 28/03/13 20:32, Ryan Ollos wrote:
> On Thu, Mar 28, 2013 at 11:58 AM, Ryan Ollos <ry...@wandisco.com>wrote:
>
>> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej <br...@wandisco.com>wrote:
>>
>>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, Mar 28, 2013 at 11:58 AM, Ryan Ollos <ry...@wandisco.com>wrote:
> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej <br...@wandisco.com>wrote:
>
>> On 28.03.2013 07:49, Ryan Ollos wrote:
>> > On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Branko Čibej <br...@wandisco.com>.
On 28.03.2013 19:58, Ryan Ollos wrote:
> On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 28.03.2013 07:49, Ryan Ollos wrote:
>>> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
Gary, as PMC chair, should have access to that.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: svn commit: r1648 - in /release/incubator/bloodhound:
apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc
apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, Mar 28, 2013 at 12:03 AM, Branko Čibej <br...@wandisco.com> wrote:
> On 28.03.2013 07:49, Ryan Ollos wrote:
> > On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz
apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Branko Čibej <br...@wandisco.com>.
On 28.03.2013 07:49, Ryan Ollos wrote:
> On Wed, Mar 27, 2013 at 11:42 PM, <rj...@apache.org> 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.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: svn commit: r1648 - in /release/incubator/bloodhound: apache-bloodhound-incubating-0.5.2.tar.gz apache-bloodhound-incubating-0.5.2.tar.gz.asc apache-bloodhound-incubating-0.5.2.tar.gz.md5
Posted by Gary Martin <ga...@wandisco.com>.
>>
>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`?
It might be worth requesting that infra migrates the directories as there may be other changes to take into account with the automated publishing, archiving of old releases and setting up of the commit notification.
I'll raise an infra ticket for that in a bit if nobody gets there first.
Cheers,
Gary