From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32674 Path: main.gmane.org!not-for-mail From: Russ Allbery Newsgroups: gmane.emacs.gnus.general Subject: Re: Oort Gnus branch Date: 01 Oct 2000 14:41:48 -0700 Organization: The Eyrie Sender: owner-ding@hpc.uh.edu Message-ID: References: <20001001164422.AD94B88F@sean.ebone.net> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035168919 21122 80.91.224.250 (21 Oct 2002 02:55:19 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:55:19 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by mailhost.sclp.com (Postfix) with ESMTP id CA648D051E for ; Sun, 1 Oct 2000 17:42:45 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id QAC05828; Sun, 1 Oct 2000 16:42:23 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 01 Oct 2000 16:41:38 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id QAA27428 for ; Sun, 1 Oct 2000 16:41:30 -0500 (CDT) Original-Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.13.23]) by mailhost.sclp.com (Postfix) with SMTP id 3A702D051E for ; Sun, 1 Oct 2000 17:41:55 -0400 (EDT) Original-Received: (qmail 26974 invoked by uid 50); 1 Oct 2000 21:41:48 -0000 Original-To: ding@gnus.org In-Reply-To: smd@ebone.net's message of "Sun, 1 Oct 2000 18:44:22 +0200 (CEST)" Original-Lines: 18 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:32674 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32674 Sean Doran writes: > 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. For INN, we copied this model and it's worked quite well. I prefer having the release on a branch; the difficulty in committing things to the branch helps make sure that only important fixes go in there. :) -- Russ Allbery (rra@stanford.edu)