You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2017/04/01 20:14:42 UTC

[jira] [Commented] (RATIS-56) Update project version to 0.1.0-alpha

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

Enis Soztutar commented on RATIS-56:
------------------------------------

Good to know, but I still think that we should commit this. The reason is that we want the release source tarball to be created from an exact git hash (or tag), so that we can verify the contents are the same as the git tag. If we do not commit this, then we will lose the property that the recursive diff of tarball vs git tag is zero. 
+1 on the patch. 
Thanks for driving the release BTW. As an RM, I think you can commit these kind of patches without having to wait for the full round of reviews just to speed things up. 
On an unrelated note, what can help us for driving frequent releases is to have a script to drive the release process. I think we should do something like this: https://github.com/apache/hbase/blob/master/dev-support/make_rc.sh. 

> Update project version to 0.1.0-alpha
> -------------------------------------
>
>                 Key: RATIS-56
>                 URL: https://issues.apache.org/jira/browse/RATIS-56
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: r56_20170330.patch
>
>
> We may use the following command to update the project version from 0.1-SNAPSHOT to 0.1.0-alpha.
> {code}
> find . -name pom.xml | xargs sed -i.old "s/0.1-SNAPSHOT/0.1.0-alpha/g" 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)