Re: GIT - releases workflow

From: Matthias Kestenholz <lists@spinlock.ch>
Date: Dec 13, 2006, 09:10 UTC
Message-ID: <1166001019.19098.4.camel@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.63.0612122353320.2807@wbgn013.biozentrum.uni-wuerzburg.de>

Hi,

On Tue, 2006-12-12 at 23:54 +0100, Johannes Schindelin wrote:

Show 10 quoted lines

> Hi,
> 
> On Tue, 12 Dec 2006, Sean Kelley wrote:
> 
> > I was wondering if anyone could share ideas on how best to use GIT to 
> > handle releases for those working with a remote GIT repository?  Do you 
> > create a branch and push it to the remote?  Thus you have a new branch 
> > referencing the particular release?
> 
> Why not just tag the release, and push the tag?

I am doing both in my web SDK project.

I currently have two branches, master and maint/v1. Over time, if necessary, I'll open new branches named maint/v2, maint/v3 etc.

New development happens on master, bugfixes go to maint/v1 and get merged into master. If I do bugfix releases (2.0.x), I tag the tip of the maint/v1 branch.

I need a full branch, because I need the ability to do bugfixes for the already-released version.

Matthias