[jira] [Commented] (OAK-4487) Move the apache-release profile in oak-parent

["Francesco Mari (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341411#comment-15341411 ] 

Francesco Mari commented on OAK-4487:
-------------------------------------

[~edivad], [~djaeggi], [~ajain], I'm wondering if there is a simpler way to enable releases of individual modules. The configuration in the {{apache-release}} generates a signed archive of the released artifacts and a vote e-mail, but none of this two steps seem to be necessary to perform a valid Apache release. I could perform a release using the configuration inherited from the Apache parent POM, and artifacts can be verified from the staging repository using the {{check_staged_release.sh}} script. Since you have way more experience than me regarding releases at Apache, can you provide your point of view on this?

> Move the apache-release profile in oak-parent
> ---------------------------------------------
>
>                 Key: OAK-4487
>                 URL: https://issues.apache.org/jira/browse/OAK-4487
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: parent
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>             Fix For: 1.6
>
>
> The {{apache-release}} profile in the root POM defines some required steps to build release artifacts in Oak. This profile should be moved to the POM in {{oak-parent}} so that these steps can be shared between different modules.
> As a concrete example, oak-segment-tar should be able to reuse these steps to be compliant with our release process. For further details, see OAK-4446.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)