You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commonsrdf.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2016/04/29 19:15:12 UTC
[jira] [Commented] (COMMONSRDF-32) Update Release Preparation with
Correct Link to CommonsRDF KEYS file
[ https://issues.apache.org/jira/browse/COMMONSRDF-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264359#comment-15264359 ]
Stian Soiland-Reyes commented on COMMONSRDF-32:
-----------------------------------------------
http://commons.apache.org/releases/prepare.html#Update_KEYS_file_if_necessary is the same for all Commons components.
Commons RDF is "special" in that we are currently in the incubator (thus our releases are done formally by the Incubator PMC) - and our KEYS file and releases are under incubator/commonsrdf/KEYS
Perhaps we should transition to a Commons Release process where we propose the RC on dev@commons and release it "the commons way"? What would be a good strategy to move towards that, Britter?
> Update Release Preparation with Correct Link to CommonsRDF KEYS file
> --------------------------------------------------------------------
>
> Key: COMMONSRDF-32
> URL: https://issues.apache.org/jira/browse/COMMONSRDF-32
> Project: Apache Commons RDF
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3.0
>
>
> There is a trivial error in the following release management content
> http://commons.apache.org/releases/prepare.html#Update_KEYS_file_if_necessary
> We should update the link to
> https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)