You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2020/02/09 16:02:00 UTC
[jira] [Comment Edited] (CASSANDRA-14963) Release artifacts should
be able to be built without being release manager
[ https://issues.apache.org/jira/browse/CASSANDRA-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033236#comment-17033236 ]
Michael Semb Wever edited comment on CASSANDRA-14963 at 2/9/20 4:01 PM:
------------------------------------------------------------------------
Being a "release manager" here is defined by the constraint of having your gpg public key listed in KEYS. Any committer can be a release manager once a PMC has added their key to the KEYS file (as only PMC can commit to https://www.apache.org/dist/cassandra/KEYS ).
Though the post-vote operation of moving staging artefacts from the dev dist location to the release dist location needs to be done by a PMC, unless the PMC votes to allow committers to.
Some work is being done under CASSANDRA-14970 to help simplify this, specifically to do as much as possible pre-vote using only committer privileges., leaving the post-vote PMC-only work as simple as possible. This also makes sense as, as little as possible should be changed or generated after the vote (otherwise it's defeating the purpose of the vote).
was (Author: michaelsembwever):
Being a "release manager" here is defined by the constraint of having you gpg public key listed in KEYS. A committer can be a release manager after a PMC has added their key to the KEYS file (as only PMC can commit to https://www.apache.org/dist/cassandra/KEYS ).
Though the post-vote operation of moving staging artefacts from the dev dist location to the release dist location needs to be done by a PMC, unless the PMC votes to allow committers to.
Some work is being done under CASSANDRA-14970 to help simplify this, specifically to do as much as possible pre-vote using only committer privileges., leaving the post-vote PMC-only work as simple as possible. This also makes sense as, as little as possible should be changed or generated after the vote (otherwise it's defeating the purpose of the vote).
> Release artifacts should be able to be built without being release manager
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-14963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14963
> Project: Cassandra
> Issue Type: Bug
> Reporter: Michael Shuler
> Priority: Normal
> Labels: packaging
>
> Currently, the release artifact build process does full maven upload of gpg-signed artifacts and package builds with repo signing. It would be helpful to be able to build and tag as a committer, then have the gpg signing as a separate event/process. The builds could be local and staged somewhere, then a release manager could verify and gpg sign the artifacts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org