public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Textrels in packages policy
Date: Wed, 14 Dec 2005 01:37:57 +0000	[thread overview]
Message-ID: <20051214013757.3b25fe22@snowdrop.home> (raw)
In-Reply-To: <20051214012029.GE1863@toucan.gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On Wed, 14 Dec 2005 01:20:29 +0000 Mike Frysinger <vapier@gentoo.org>
wrote:
| the policy i consider a no-brainer, fix TEXTRELs

So... Say libfoo is a library that decodes files in the foo format. Say
also that libfoo-2.1 is currently marked stable, and does not contain
any TEXTRELs, but only supports foo files using the foo-1 format, which
is rapidly becoming obsolete. Then, if libfoo-2.2 comes along, and
introduces support for the rapidly becoming very widely used foo-2
format, should libfoo-2.2 be held back from being marked stable purely
because of a TEXTREL?

What about if, instead, libfoo-2.1 contains a security bug that is
fixed by libfoo-2.2?

What about if, instead, libfoo-2.1 has a nasty bug that will cause it
to lose data under certain circumstances?

See, any policy on TEXTRELs will have to be *very* carefully worded to
avoid having people think that they're something important... Otherwise
we'll end up with broken packages being left in stable simply because
newer versions contain TEXTRELs. Don't overhype the problem -- make it
clear that it's a "would be nice" issue, or else you'll encourage even
more superstition than we have already...

-- 
Ciaran McCreesh : Gentoo Developer (I can kill you with my brain)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-14  1:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 20:59 [gentoo-dev] Textrels in packages policy Mark Loeser
2005-12-13 21:15 ` Mike Frysinger
2005-12-13 22:30 ` Saleem A.
2005-12-14  0:22   ` Mike Frysinger
2005-12-14  1:02     ` Mark Loeser
2005-12-14  1:16       ` Ciaran McCreesh
2005-12-14  1:20       ` Mike Frysinger
2005-12-14  1:37         ` Ciaran McCreesh [this message]
2005-12-14  1:43           ` Mike Frysinger
2005-12-14  1:39         ` Mark Loeser
2005-12-14  1:07     ` Ciaran McCreesh
2005-12-14  1:25       ` Mike Frysinger
2005-12-14  1:32         ` Mark Loeser
2005-12-13 23:59 ` Jory A. Pratt
2005-12-14  0:25   ` Mike Frysinger
2005-12-14  2:59     ` Jason Wever
2005-12-14  3:08       ` Mark Loeser
2005-12-14  3:50       ` Mike Frysinger
2005-12-14  6:59         ` Harald van Dijk
2005-12-14  7:51           ` Kevin F. Quinn
2005-12-14  8:19             ` Harald van Dijk
2005-12-14 13:43               ` Mike Frysinger
2005-12-14 14:27                 ` Harald van Dijk
2005-12-14 14:38                   ` Mike Frysinger
2005-12-14 15:04                     ` Harald van Dijk
2005-12-15  7:14               ` Kevin F. Quinn
2005-12-14 15:25     ` Chris Gianelloni
2005-12-14 15:27     ` Chris Gianelloni
2005-12-14 15:42       ` Mike Frysinger
2005-12-14  7:44 ` Kevin F. Quinn
2005-12-14  9:33   ` Henrik Brix Andersen

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=20051214013757.3b25fe22@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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