public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Langer <mlangc@gmx.at>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: firefox-1.5.x still in ~arch
Date: Sun, 19 Mar 2006 16:11:53 +0100	[thread overview]
Message-ID: <1142781113.19054.8.camel@sputnik886.ruz-net> (raw)
In-Reply-To: <pan.2006.03.19.14.56.22.98471@cox.net>

On Sun, 2006-03-19 at 07:56 -0700, Duncan wrote:
> Matthias Langer posted <1142778259.17324.16.camel@sputnik886.ruz-net>,
> excerpted below,  on Sun, 19 Mar 2006 15:24:19 +0100:
> 
> > I'm just curious: What is the reason that firefox-1.5.x is still in
> > ~arch ?
> 
> General policy is that an ebuild should be bug-free in ~arch for 30 days
> before it is stabilized.  Individual herds and maintainers may have their
> own policies, but the above 30 day guideline is the general Gentoo rule of
> thumb.
> 
> Looking at the changelog, mozilla-firefox-1.5.0.1-r2 was only added to the
> tree on February 24.  The -r2 indicates updates serious enough to bump the
> release number were released at least twice, and the 1.5 ebuilds are at
> -r9, indicating 10 versions (the first being -r0, not marked with an
> release number, of course).
> 
> That's a /lot/ of versions!  I'd guess there have simply been enough
> issues that no version of 1.5 has yet made it 30 days bug-free in ~arch,
> altho the .0.1-r2 version above is getting close to 30 days in ~arch now,
> tho I don't know its bug status.
> 
> I often check the portage tree changelogs and Gentoo bugzilla site status
> of particular packages that I'm interested in.  I'm glad the info is
> available, as it has proven useful quite often.
> 
> -- 
Thanks for your answer; however, i've seen new versions of firefox
getting from ~arch to stable much faster than 30 days, but i guess that
was because of security issues; by the way, i was happy to read

"
*mozilla-firefox-1.5.0.1-r1 (09 Feb 2006)

  09 Feb 2006; <anarchy@gentoo.org> +mozilla-firefox-1.5.0.1-r1.ebuild:
  official branding support, ewarn about regchrome
"

that gentoo now has official branding support ...

Matthias


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-03-19 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 14:24 [gentoo-dev] firefox-1.5.x still in ~arch Matthias Langer
2006-03-19 14:56 ` [gentoo-dev] " Duncan
2006-03-19 15:11   ` Matthias Langer [this message]
2006-03-19 18:13 ` [gentoo-dev] " Patrick Lauer

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=1142781113.19054.8.camel@sputnik886.ruz-net \
    --to=mlangc@gmx.at \
    --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