My apologies! Only PMCs can sign releases.
This should not be a problem. When you start the release process, simply
let a PMC know that you'd like them to build the release and sign them.
They will then upload it to dist.apache.org and you can point to them in
your message for voting.
Francis
On 18/06/2018 9:37 PM, Vova Vysotskyi wrote:
Thanks for the response.
I tried to commit my changes in KEY file using my commiters credentials,
and looks like I don't have an access:
svn ci -m "Add Volodymyr Vysotskyi's key to KEYS file"
Sending KEYS
Transmitting file data .svn: E195023: Commit failed (details follow):
svn: E195023: Changing file '/home/user515050/dist/KEYS' is forbidden by
the server
svn: E175013: Access to
'/repos/dist/!svn/txr/27525-nbx/release/calcite/KEYS' forbidden
Also, I found a similar problem in
https://issues.apache.org/jira/browse/INFRA-13997.
There was mentioned that only PMCs have access to update the dist/release/
tree.
Kind regards,
Volodymyr Vysotskyi
пн, 18 черв. 2018 о 14:06 Francis Chuang <[email protected]> пише:
Hey Volodymyr,
https://dist.apache.org/repos/dist/release/calcite/ is used for
publishing releases. Simply access it using SVN (with your committer
credentials). Add your key to the KEYS file and you should be good to go.
Francis
On 18/06/2018 8:56 PM, Volodymyr Vysotskyi wrote:
Hi all,
Instruction for Calcite release contains point where a public key should
be
added to the KEYS file.
Is this file in https://dist.apache.org/repos/dist/release/calcite/
taken
from a mirror in another place, or it should be modified in this place?
Also, in the instructions for other projects, I found that svn may be
used
to push changes directly to the dist.apache.org, but I think I don't
have
an access to do that.
Kind regards,
Volodymyr Vysotskyi
