You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2015/09/02 00:22:46 UTC

[jira] [Commented] (SAMZA-725) Fix RELEASE.md document

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

Navina Ramesh commented on SAMZA-725:
-------------------------------------

+1 for the patch. I didn't really test the steps.Can't do it without releasing :) 
Looks good for committing though!



> Fix RELEASE.md document
> -----------------------
>
>                 Key: SAMZA-725
>                 URL: https://issues.apache.org/jira/browse/SAMZA-725
>             Project: Samza
>          Issue Type: Bug
>          Components: release doc
>    Affects Versions: 0.9.1
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Yi Pan (Data Infrastructure)
>             Fix For: 0.10.0
>
>         Attachments: SAMZA-725-1.patch, SAMZA-725.patch
>
>
> During the process to release 0.9.1, I noticed a few issues in the RELEASE.md:
> # ./gradlew licenseFormatMain fails
> # After {code}git tag -s release-$VERSION-rc0 -m "Apache Samza $VERSION release candidate 0"{code}, the tag is still not in the remote repo, we need to do: {code}git push origin release-$VERSION-rc0{code}
> # We need to remove all -PscalaVersion=2.10 since default is now 2.10



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