X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20140318195939.14238.qmail@stuge.se>
Date: Tue, 18 Mar 2014 20:59:39 +0100
From: Peter Stuge <peter AT stuge DOT se>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] pcb-20140316 is released
Mail-Followup-To: geda-user AT delorie DOT com
References: <201403170355 DOT s2H3tavv007601 AT envy DOT delorie DOT com> <532741F8 DOT 8090101 AT buffalo DOT edu> <201403171845 DOT s2HIj1kj012076 AT envy DOT delorie DOT com> <53282C68 DOT 3040908 AT prochac DOT sk> <201403181659 DOT s2IGxV8R011102 AT envy DOT delorie DOT com> <5328A141 DOT 4000405 AT prochac DOT sk> <201403181942 DOT s2IJgwwr018329 AT envy DOT delorie DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201403181942.s2IJgwwr018329@envy.delorie.com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

DJ Delorie wrote:
> > But the result is IMO  confusing...
> 
> How so?  There's a branch for the 20140316 release named pcb-20140316.

I'd usually expect a tag rather than a branch for a release.

A branch would only be created later, in case there would be some
bugfix release e.g. with changes backported from the master branch.

This would also fit well with git describe --tags output.


//Peter