public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Andersson <snikkt@telia.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Is there a process for marking ebuilds stable?
Date: Mon, 14 Apr 2003 16:29:59 +0000	[thread overview]
Message-ID: <200304141630.02243.snikkt@telia.com> (raw)
In-Reply-To: <20030414110436.GC441@pobox.com>

On Monday 14 April 2003 11.04, Fredrik Jagenheim wrote:
>
> However, a successful emerge is only one of the critieria for an
> unstable package to move to stable. It not crashing runtime is
> another...
>
> Actually, the more I think of it, the whole point is moot...
> stable.gentoo.org might be a good idea, but why not replace it with
> stats.gentoo.org? If I submit a stat report which tells me that I have
> the latest version of a package installed, you could assume that it
> works for me. If not, I'd post a bugreport. And if I couldn't be arsed
> to set up gentoo-stats and post bugs about things that doesn't work,
> why would I use stable.gentoo.org anyway?
>
I don't think stable.gentoo.org is not a good solution since it's too much
manual work included from a user for (apparently nothing) in return.

I think the most efficient way to mark packages stable is statistics based.

If you compare number of installations of a  package against number of bugs
filed and their severity i think you should get pretty decent stability 
figures for most packages. The exception to this is packages with few users
but the users of such packages is probably more interested in 'voting' for 
their packages.

This is only an initial suggestion, please comment and improve :)

1) Successful Emerges/Bugs
  a) Count package downloads and bugs filed. If no blocker/critical bugs 
exists after a week or two mark as stable. For important packages this rule
could be made more stringent.
  b) Count real merges/unmerges of packages and not only package downloads, 
this should to opt-in since it would in some way need to post information 
back to gentoo.org

2) Voting console
A console application which finds all stable packages installed more than
a week or two ago and asks you to determine how much you've used them.
As default it only needs to show packages with few users since simple 
statistics should be enough to validate packages with many users. At the
end of the emerge remind a user of 'unpopular' packages to run the voting
console to mark as stable.

> Please, don't see this as an attack on stable.gentoo.org, just trying
> to see it in another perspective... And I probably missed something in
> that generalization...
>
> > Sorry for this rather long a quite unfocussed post, mid-term exams are
> > on the horizon again so I maybe should just shut up and grab my books...
>
> Exams are important, but so is gentoo. ;)
>
+1

> //H


/Mikael Andersson

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-14 14:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13 22:25 [gentoo-dev] Is there a process for marking ebuilds stable? Brad Laue
2003-04-13 23:00 ` Rainer Groesslinger
2003-04-13 23:07   ` Rainer Groesslinger
2003-04-13 23:07   ` Jon Portnoy
2003-04-14  9:31     ` Rainer Groesslinger
2003-04-14  7:32   ` Fredrik Jagenheim
2003-04-14  9:00     ` Michael Kohl
2003-04-14 11:04       ` Fredrik Jagenheim
2003-04-14 16:29         ` Mikael Andersson [this message]
2003-04-14 20:31           ` Alec Berryman
2003-04-14 21:48             ` Brad Laue
2003-04-14 21:58               ` Alec Berryman
2003-04-15 11:07                 ` Mikael Andersson
2003-04-14 22:03           ` Brad Laue
2003-04-14 15:07     ` Brad Laue
2003-04-14 19:39       ` C. Brewer
2003-04-15  6:21         ` Abhishek Amit
2003-04-15  9:09           ` Fredrik Jagenheim
2003-04-16  0:34           ` C. Brewer
2003-04-15 13:53         ` Brad Laue
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15  2:08 Todd Wright
2003-04-15  2:30 ` Jon Portnoy
2003-04-15  5:41 ` Dylan Carlson

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=200304141630.02243.snikkt@telia.com \
    --to=snikkt@telia.com \
    --cc=gentoo-dev@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