[
https://issues.apache.org/jira/browse/FLINK-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929365#comment-15929365
]
shijinkui commented on FLINK-5754:
----------------------------------
[~greghogan] I had checkout a branch from tag 1.2 in produce. In general
release tag is the final version, not the branch. Am I right?
IMO, the release tag commit only change the project version, and shouldn't
change any others except version number.
I look some other apache project, they follow this rule. Can we consider this
normal rule? Must the hidden files be deleted in the release tag?
https://github.com/apache/spark/commit/cd0a08361e2526519e7c131c42116bf56fa62c76
https://github.com/apache/hadoop/commit/94152e171178d34864ddf6362239f3c2dda0965f
https://github.com/apache/storm/commit/eac433b0beb3798c4723deb39b3c4fad446378f4
> released tag missing .gitigonore .travis.yml .gitattributes
> ------------------------------------------------------------
>
> Key: FLINK-5754
> URL: https://issues.apache.org/jira/browse/FLINK-5754
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Reporter: shijinkui
>
> released tag missing .gitigonore .travis.yml .gitattributes.
> When make a release version, should only replace the version.
> for example: https://github.com/apache/spark/tree/v2.1.0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
