public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Should "orphan" package without any "stable" version be stabilized?
Date: Thu, 24 Jun 2010 17:54:03 +0200	[thread overview]
Message-ID: <1277394843.25546.41.camel@localhost.localdomain> (raw)
In-Reply-To: <20100624174444.72c0cab1@gentoo.org>

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

El jue, 24-06-2010 a las 17:44 +0200, Christian Faulhammer escribió:
> Hi,
> 
> Pacho Ramos <pacho@gentoo.org>:
> > app-office/ledger doesn't have any maintainer and has no stable
> > version, also, seems that no other app requires this to be
> > stabilized. I would prefer to keep this in testing until a maintainer
> > really maintains it downstream, but I am not sure if there is already
> > some policy on this :-/
> 
>  Generally it should not be stabilised.  But based on common sense
>  (simple program, no dependencies), you could do it.
> 
> V-Li
> 

OK, I was doubtful because when a package lacks maintainer, maybe it's
not fully tested and some bugs could be opened and, then, rarely fixed
(as they would be assigned to maintainer-needed). On the other hand, I
would hope that preserving those packages in "testing", their users
wouldn't expect it to be as "stable" and "properly maintained" as a
package marked "stable".

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-06-24 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 13:32 [gentoo-dev] Should "orphan" package without any "stable" version be stabilized? Pacho Ramos
2010-06-24 15:44 ` [gentoo-dev] " Christian Faulhammer
2010-06-24 15:54   ` Pacho Ramos [this message]

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=1277394843.25546.41.camel@localhost.localdomain \
    --to=pacho@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