Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Version numbering
Date: Tue, 22 Feb 2011 08:32:09 +0100	[thread overview]
Message-ID: <yb07hcs8qyu.fsf@dod.no> (raw)
In-Reply-To: <874o7xklr9.fsf@gnus.org>

>>>>> Lars Ingebrigtsen <larsi@gnus.org>:

> Richard Riley <rileyrg@googlemail.com> writes:
>> Why not only tag releases and then use a development branch for all
>> ongoing work until the next merge and tag release party?

> Development happens on the trunk.

Then you could make a branch called "releases".

If there hasn't been anything happening on the release branch since the
last release, doing a merge from master is a simple (and low-cost (since
it will be a ff-merge)) operation:
 git checkout releases
 git merge master
thazzit!

You could put a tag on releases after the merge master.

The releases branch will become an exact copy of master, but
time-deleayed.








  reply	other threads:[~2011-02-22  7:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 23:07 Lars Ingebrigtsen
2011-02-21 23:27 ` Richard Riley
2011-02-21 23:31   ` Lars Ingebrigtsen
2011-02-22  7:32     ` Steinar Bang [this message]
2011-02-23  8:07       ` Lars Ingebrigtsen
2011-02-23 10:21         ` Julien Danjou
2011-02-23 10:31           ` Lars Ingebrigtsen
2011-02-23 10:44           ` Steinar Bang
2011-02-23 11:36             ` Julien Danjou
2011-02-21 23:48 ` Andreas Schwab
2011-02-22  0:01   ` Lars Ingebrigtsen
2011-02-22 15:21 ` Julien Danjou
2011-02-23  8:08   ` Lars Ingebrigtsen
2011-02-23 10:17     ` Julien Danjou
2011-02-23 10:26       ` Erik Colson
2011-02-23 10:43         ` Steinar Bang
2011-02-23 10:29       ` Lars Ingebrigtsen

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=yb07hcs8qyu.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).