The pattern I've liked the most on other projects is to create a proper release tag, signed by the RM on passage of the release vote. I don't recall off-hand what the phrasing was in the VOTE thread (if any).
On Mon, Sep 21, 2015 at 8:13 AM, Adam Taft <a...@adamtaft.com> wrote: > What's the thoughts on creating a proper 0.3.0 tag, as would be traditional > for a final release? It is arguably a little confusing to only have the RC > tags, when looking for the final release. I found this head scratching for > 0.2.0 as well. > > Adam > > > On Mon, Sep 21, 2015 at 7:44 AM, Esteban Aliverti < > esteban.alive...@gmail.com> wrote: > >> Thanks! >> >> >> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >> >> Esteban Aliverti >> - Blog @ http://ilesteban.wordpress.com >> >> On Mon, Sep 21, 2015 at 12:21 PM, Joe Witt <joe.w...@gmail.com> wrote: >> >> > Esteban >> > >> > The tag you mention is the correct tag for the 0.3.0 source. >> > >> > Thanks >> > Joe >> > On Sep 21, 2015 4:43 AM, "Esteban Aliverti" <esteban.alive...@gmail.com> >> > wrote: >> > >> > > Hi there, >> > > I want to give v. 0.3.0 a try and I would like to know where the source >> > > code for that version is. >> > > Right now, master has 0.3.1-SNAPSHOT version. I noticed there is a >> > > nifi-0.3.0-RC1 >> > > < >> > > >> > >> https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=commit;h=2ec735e35025fed3c63d51128ec0609ffe1fa7e3 >> > > > >> > > tag >> > > that has 0.3.0 version in its poms. Should I use 0.3.0-RC1 then? Is >> this >> > > branch already frozen? It will be any other branch for 0.3.0 final? >> > > >> > > Regards, >> > > >> > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >> > > >> > > Esteban Aliverti >> > > - Blog @ http://ilesteban.wordpress.com >> > > >> > >> -- Sean
