Gnus development mailing list
 help / color / mirror / Atom feed
From: smd@ebone.net (Sean Doran)
Cc: ding@gnus.org
Subject: Re: Oort Gnus branch
Date: Sun,  1 Oct 2000 18:44:22 +0200 (CEST)	[thread overview]
Message-ID: <20001001164422.AD94B88F@sean.ebone.net> (raw)


| Another thought is that maybe we would like to do it like Emacs does
| it.  So, how does Emacs handle the branches?

NetBSD creates a tag to represent a forthcoming release; ongoing day-to-day
"-current" development continues in the trunk, while changes to
the potential-release-tag may be pulled-up only by a "release engineer".
Generally only important bug fixes, rather than new features, are pulled up.

At some point the releng folks are satisfied that the branch is ready
to be tarred up as an actual release, and out goes the latest non-CVS version.

Likewise, critical fixes can be pulled up into older already-released
branches, for the benefit of people who deliberately run older releases
for stability or other reasons.  

	Sean.



             reply	other threads:[~2000-10-01 16:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-01 16:44 Sean Doran [this message]
2000-10-01 18:59 ` Kai Großjohann
2000-10-01 21:41 ` Russ Allbery
  -- strict thread matches above, loose matches on Subject: below --
2000-09-30 23:41 ShengHuo ZHU
2000-10-01  6:14 ` Norbert Koch
2000-10-01 11:45   ` ShengHuo ZHU
2000-10-01 12:11     ` Kai Großjohann
2000-10-01 12:25       ` Daniel Pittman
2000-10-01 12:34         ` Norbert Koch
2000-10-01 13:20         ` ShengHuo ZHU
2000-10-01 13:56           ` William M. Perry
2000-10-03 22:47             ` Dave Love
2000-10-01 12:48       ` Bruce Stephens
2000-10-01 12:19     ` Karl Eichwalder
2000-10-01 16:49 ` Florian Weimer

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=20001001164422.AD94B88F@sean.ebone.net \
    --to=smd@ebone.net \
    --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).