incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release Apache Calcite 0.9.1 (incubating)
Date Fri, 10 Oct 2014 00:19:14 GMT
On 10 October 2014 00:54, Julian Hyde <julianhyde@gmail.com> wrote:
>
> On Oct 9, 2014, at 4:41 PM, sebb <sebbaz@gmail.com> wrote:
>
>> On 9 October 2014 21:14, Julian Hyde <julianhyde@gmail.com> wrote:
>>> That information is all in the vote proposal: http://mail-archives.apache.org/mod_mbox/incubator-optiq-dev/201410.mbox/%3CCAMCtmeL%2Bgcf1yamWqRicpUJxU2tkyqGEzojd9nNXKmdEE3QwQQ%40mail.gmail.com%3E
>>>
>>> I’ll repeat it here:
>>>
>>> The commit to be voted upon:
>>> http://git-wip-us.apache.org/repos/asf/incubator-optiq/commit/6801257324d7515f91c61877a0edd0863c0433f5
>>>
>>> The artifacts to be voted on are located here:
>>> http://people.apache.org/~jhyde/apache-calcite-0.9.1-incubating-rc1/
>>
>> What about the hashes please?
>
> I don’t understand. http://people.apache.org/~jhyde/apache-calcite-0.9.1-incubating-rc1/
contains two tar balls (.tar.gz and .zip) and each has a corresponding .asc, .md5, .sha1 file.
What other hashes are needed?

Those hashes need to be quoted in the vote e-mail.
Otherwise it is not possible to prove that the vote was was performed
on the same artifacts as the ones that are published.

The URL (and files) are transient and mutable.

But if the SHA1 of the tarballs are shown in the vote e-mail, then
this should be sufficient to show that the vote took place on the same
artifacts that were eventually published.

> If you mean the git commit hash, that is simply the commit id: 6801257324d7515f91c61877a0edd0863c0433f5.
>
>>
>>> A staged Maven repository is available for review at:
>>> https://repository.apache.org/content/repositories/orgapachecalcite-1000
>>>
>>> Release artifacts are signed with the following key:
>>> https://people.apache.org/keys/committer/jhyde.asc
>>
>> Ideally please show the URL that will be included on the download page, e.g.
>>
>> http://www.apache.org/dist/incubator/amber/KEYS
>>
>> There was no calcite directory, so I created it.
>>
>> It should be sufficient to add the KEYS file to
>>
>> https://dist.apache.org/repos/dist/release/incubator/calcite/
>>
>> By the magic of svnpubsub it will then appear at
>>
>> http://www.apache.org/dist/incubator/calcite/
>>
>> Note: I also created
>> https://dist.apache.org/repos/dist/dev/incubator/calcite
>> which can be used for future release candidates.
>
> Yes, I would have populated those locations but I am still waiting on https://issues.apache.org/jira/browse/INFRA-8418.

I see. Oops. I have removed the empty release directory as it may
interfere with the Infra issue.

I will leave the dev directory as there was no optiq one

> Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message