All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Release Policy [was: Linux 2.4.16  ]
Date: Mon, 26 Nov 2001 10:31:41 -0800	[thread overview]
Message-ID: <3C028A8D.8040503@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111261216500.88-100000@rc.priv.hereintown.net> <Pine.LNX.4.21.0111261351160.13786-100000@freak.distro.conectiva> <9tu0n2$sav$1@cesium.transmeta.com> <20011126192902.M5770@khan.acc.umu.se>

David Weinehall wrote:

>>
>>Oh, and yes, if you settle on a naming scheme, *please* let me know
>>ahead of time so I can update the scripts to track it, rather than
>>finding out by having hundreds of complaints in my mailbox...
>>
> 
> I for one used the -pre and -pre-final naming for the v2.0.39-series,
> and I'll probably use the same naming for the final pre-patch of
> v2.0.40, _unless_ there's some sort of agreement on another naming 
> scheme. I'd be perfectly content with using the -rc naming for the
> final instead. The important thing is not the naming itself, but
> consistency between the different kernel-trees.
> 


Consistency is a Very Good Thing[TM] (says the one who tries to teach
scripts to understand the naming.)  The advantage with the -rc naming is
that it avoids the -pre5, -pre6, -pre-final, -pre-final-really,
-pre-final-really-i-mean-it-this-time phenomenon when the release
candidate wasn't quite worthy, you just go -rc1, -rc2, -rc3.  There is no
shame in needing more than one release candidate.

	-hpa



  reply	other threads:[~2001-11-26 18:34 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0111261003070.13400-100000@freak.distro.cone ctiva>
2001-11-26 16:38 ` Release Policy [was: Linux 2.4.16 ] David Relson
2001-11-26 15:33   ` Marcelo Tosatti
2001-11-26 17:14     ` David Relson
2001-11-26 21:15       ` Bill Davidsen
2001-11-26 17:22     ` Chris Meadors
2001-11-26 15:54       ` Marcelo Tosatti
2001-11-26 17:41         ` David Rees
2001-11-26 18:12         ` H. Peter Anvin
2001-11-26 18:29           ` David Weinehall
2001-11-26 18:31             ` H. Peter Anvin [this message]
2001-11-26 17:25               ` Marcelo Tosatti
2001-11-26 18:49                 ` H. Peter Anvin
2001-11-26 19:00                 ` François Cami
2001-11-26 19:06                 ` Jonathan Lundell
2001-11-26 19:28                   ` Flavio Stanchina
2001-11-26 19:43                     ` Jonathan Lundell
2001-11-26 19:36                 ` David Weinehall
2001-11-26 20:39                 ` junio
2001-11-26 20:55                   ` David Weinehall
2001-11-26 20:59                     ` H. Peter Anvin
2001-11-26 21:18               ` Gregory Maxwell
2001-11-27  8:02                 ` Svein Erik Brostigen
2001-11-27  8:28                   ` Allan Sandfeld
2001-11-27  9:08                     ` Svein Erik Brostigen
2001-11-27 10:07                 ` Alex Bligh - linux-kernel
2001-11-27 14:43                 ` Sven Vermeulen
2001-11-27 15:01                   ` Ian Molton
2001-11-27 15:42                   ` John Alvord
2001-11-27 16:03                   ` Michel Angelo da Silva Pereira
2001-11-26 18:48       ` Bjoern A. Zeeb
2001-11-26 23:15         ` J.A. Magallon
2001-11-27  1:04     ` Andrew Morton
2001-11-27  1:13       ` Release Policy David S. Miller
2001-11-27  1:32         ` H. Peter Anvin
2001-11-27  7:39           ` Anuradha Ratnaweera
2001-11-27  7:40             ` H. Peter Anvin
2001-11-27  7:53               ` Anuradha Ratnaweera
2001-11-27 10:08             ` Harald Arnesen
2001-11-27 10:29               ` Keith Owens
2001-11-27 19:45                 ` Mike Fedyk
2001-12-05 14:27         ` Jes Sorensen
2001-11-26 17:52 Release Policy [was: Linux 2.4.16 ] Dana Lacoste
2001-11-26 17:59 ` John Jasen
2001-11-27  7:41 ` Anuradha Ratnaweera
2001-11-27 20:16   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2001-11-28 12:54 Per-Olof Pettersson
2001-11-28 12:57 Per-Olof Pettersson

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=3C028A8D.8040503@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tao@acc.umu.se \
    /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.