Re: [boost] [git] tagging in modules

Subject: Re: [boost] [git] tagging in modules
From: Ahmed Charles (acharles_at_[hidden])
Date: 2014-01-04 06:38:49

> Date: Mon, 30 Dec 2013 12:02:58 -0500
> From: bdawes_at_[hidden]
> To: boost_at_[hidden]
> Subject: Re: [boost] [git] tagging in modules
> 
> On Thu, Dec 26, 2013 at 7:24 PM, Peter A. Bigot <pab_at_[hidden]> wrote:
> 
> > On 12/26/2013 05:09 PM, Beman Dawes wrote:
> >
> >> See
> >>
> > > https://svn.boost.org/trac/boost/wiki/StartModMaint#
> > Lightweightlibraryrelease
> >
> > Not relevant to the original thread, but since I just noticed it:
> >
> > git-push by default does not push tags: you need to specifically ask for
> > the tag to be pushed (by name), or use --tags.  So this sequence does
> > nothing visible:
> >
> >  git tag -a 1.2
> >  git push
> >
> > Personally I'd prefer if tag symbols were a little more informative than
> > "1.2", and followed a pattern that places them in a namespace reserved for
> > the module, such as timer-1.2.  Because tags aren't normally pushed,
> > they're useful for individual developers to use as markers.  However,
> > git-pull will automatically retrieve tags attached to commits that are
> > fetched unless --no-tags is given, so if a repository (from boostorg, or
> > another developer) defines (or moves) a tag it might overwrite your local
> > tag without warning.  So it's important to know what tags you can expect
> > might conflict with those in a remote repository to avoid conflicts.
> >
> 
> Updated:
> 
> https://svn.boost.org/trac/boost/wiki/StartModWorkflow#Releasetags
> <https://svn.boost.org/trac/boost/wiki/StartModMaint#Lightweightlibraryrelease>
> https://svn.boost.org/trac/boost/wiki/StartModMaint
> #Lightweightlibraryrelease<https://svn.boost.org/trac/boost/wiki/StartModMaint#Lightweightlibraryrelease>

Note: git doesn't overwrite local tags with remote ones, so once you push a tag, that tag should never be moved. There's discussion of this in the documentation.