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

["Davide Giannella (JIRA)" <ji...@apache.org>]

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

Davide Giannella edited comment on OAK-4487 at 6/21/16 10:12 AM:
-----------------------------------------------------------------

{{check_staged_release.sh}} does not perform all the checks as our release process. It simply download locally all the binaries and checks the MD5/SHA1. Feel free to rename the script if you feel like.

I think if you want to individually release the oak-segment-tar bundle, you'll have to create the dedicated apache-release profile. It will share most of the things with other project but it will be slightly different as it cares on only 1 bundle.

plus the current release actually creates a tag in svn as jackrabbit-oak and then the script we run for checking the release, checks the sources of the zip file against the tag. https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh.

So this is another step to be taken into consideration.

I would say that first we have to have a proper understanding of each step that an oak release goes through (I don't have a detailed knowledge there) and then we should try to replicate those for oak-segment-tar.

An easier way would be to simply allow oak-segment-tar to be deployed along with the normal oak release. That would simplify things.


was (Author: edivad):
{{check_staged_release.sh}} does not perform all the checks as our release process. It simply download locally all the binaries and checks the MD5/SHA1.

I think if you want to individually release the oak-segment-tar bundle, you'll have to create the dedicated apache-release profile. It will share most of the things with other project but it will be slightly different as it cares on only 1 bundle.

plus the current release actually creates a tag in svn as jackrabbit-oak and then the script we run for checking the release, checks the sources of the zip file against the tag. https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh.

So this is another step to be taken into consideration.

I would say that first we have to have a proper understanding of each step that an oak release goes through (I don't have a detailed knowledge there) and then we should try to replicate those for oak-segment-tar.

An easier way would be to simply allow oak-segment-tar to be deployed along with the normal oak release. That would simplify things.

> 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)