[
https://issues.apache.org/jira/browse/PHOENIX-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121453#comment-14121453
]
Gabriel Reid commented on PHOENIX-1235:
---------------------------------------
+1, the releases should include the step of setting the current version to a
snapshot (or use the maven release plugin to do this automatically?). Having a
release version in the development pom can cause all kinds of difficult to
track down issues.
[~jamestaylor] [~mujtabachohan] I seem to remember there being a document (or
plans for a document) on performing releases, or even a script for it
somewhere? This should probably be added there.
> Release workflow – Snapshots
> ----------------------------
>
> Key: PHOENIX-1235
> URL: https://issues.apache.org/jira/browse/PHOENIX-1235
> Project: Phoenix
> Issue Type: Bug
> Reporter: Dan Di Spaltro
> Priority: Minor
>
> I would propose to adopt incrementing and -SNAPSHOT to current branches that
> aren't part of a release. It basically makes it a lot easier for new people
> to test branches after issuing a mvn install command. Right now on the 4.0.0
> branch (which is misleading but I think I remember discussion on you guys
> were fixing that) its still pinned to 4.1.0.
> Something like:
> Go through RC cycle
> Vote final release
> immediately commit increment and snapshot
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
