All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kestenholz <lists@spinlock.ch>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Sean Kelley <sean.v.kelley@gmail.com>, git@vger.kernel.org
Subject: Re: GIT - releases workflow
Date: Wed, 13 Dec 2006 10:10:19 +0100	[thread overview]
Message-ID: <1166001019.19098.4.camel@localhost.localdomain> (raw)
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:
> 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

  reply	other threads:[~2006-12-13  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 22:44 GIT - releases workflow Sean Kelley
2006-12-12 22:54 ` Johannes Schindelin
2006-12-13  9:10   ` Matthias Kestenholz [this message]
2006-12-13 10:36     ` Johannes Schindelin
2006-12-13 10:56       ` Shawn Pearce
2006-12-13 11:14         ` Shawn Pearce
2006-12-13 12:34     ` Sean Kelley
2006-12-13 12:39       ` Sean Kelley
2006-12-13 13:13         ` Andreas Ericsson
2006-12-13  2:43 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1166001019.19098.4.camel@localhost.localdomain \
    --to=lists@spinlock.ch \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sean.v.kelley@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.