+1 and, done ----- Original Message ----- > Is there a problem with tagging the last rc version with the actual > released version when you release? > > That is, part of the release process being: > > git tag -s 4.1.2 4.1.2-rc0 > > If 4.1.2-rc0 is signed and trusted, then creating another tag off this > seems fine. > > -B > > -- > Brian Rectanus | brecta...@qualys.com > > On Mon, Jan 6, 2014 at 3:09 PM, Igor Galić <i.ga...@brainsware.org> wrote: > > > > > > > ----- Original Message ----- > > > I sent this previously, but as a reply to the announcement which may have > > > gotten filtered... > > > > > > Please, can someone tag 4.1.2 in git? There is only a 4.1.2-rc0, > > currently. > > > > > > > 4.1.2-rc0 was released as 4.1.2 > > > > I didn't re-tag it, because it would have created a new it would have > > created a new signature. An idea I didn't like, but git doesn't let me > > rename tags, which, especially with signed tags makes sense. > > > > So the question is, how do we best do this? > > > > I'm pretty and sure I've asked that question already a month or so ago > > but no one's come up with a smart answer.. > > > > > Cheers! > > > -B > > > > > > -- > > > Brian Rectanus | brecta...@qualys.com > > > > > > > -- > > Igor Galić > > > > Tel: +43 (0) 664 886 22 883 > > Mail: i.ga...@brainsware.org > > URL: http://brainsware.org/ > > GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641 > > > > >
-- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641
