From: Wernfried Haas <amne@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] first council meeting
Date: Sun, 18 Sep 2005 08:46:37 +0200 [thread overview]
Message-ID: <20050918064637.GB18094@superlupo.rechner> (raw)
In-Reply-To: <200509171617.10869.vapier@gentoo.org>
On Sat, Sep 17, 2005 at 04:17:10PM -0400, Mike Frysinger wrote:
> i really want to get away from the idea of 'package.mask is for testing
> packages' ... its current dual role as both masking 'testing' packages and
> 'broken' packages is wrong imo
>
> we dont want to try reeducating our users to not be afraid of package.mask
> because a lot of things in there they *should* be afraid of
Coming from the user side (forums) i fully agree. Common sense among
the users always used to be:
arch: stable
~arch: testing
p.mask: broken
This is also covered in our current documentation, see
http://www.gentoo.org/doc/en/handbook/hb-portage-branches.xml
--snip--
The Testing Branch
If you want to use more recent software, you can consider using the
testing branch instead. To have Portage use the testing branch, add a
~ in front of your architecture.
The testing branch is exactly what it says - Testing. If a package is
in testing, it means that the developers feel that it is functional
but has not been thoroughly tested. You could very well be the first
to discover a bug in the package in which case you could file a
bugreport to let the developers know about it.
Beware though, you might notice stability issues, imperfect package
handling (for instance wrong/missing dependencies), too frequent
updates (resulting in lots of building) or broken packages. If you do
not know how Gentoo works and how to solve problems, we recommend that
you stick with the stable and tested branch.
--snip--
Doesn't exactly sound like packages in ~arch should be ready to enter
arch after 30 days (and or the other QA requirements). If someone
wants to change that, that would be a major change to Gentoo,
especially as it affects _every_ user. So it would at least require a
GLEP to do that.
I'd rather like to finally see proper QA applied and those who don't
beaten with a stick than making fundamental changes to existing common
sense just because it is written down somewhere _that_ way.
cheers,
Wernfried
--
Wernfried Haas (amne) - amne at gentoo dot org
Gentoo Forums: http://forums.gentoo.org
IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-18 6:48 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:51 [gentoo-dev] first council meeting Aron Griffis
2005-09-15 21:25 ` Olivier Crete
2005-09-15 21:57 ` Chris Gianelloni
2005-09-15 22:20 ` Mike Frysinger
2005-09-16 17:42 ` Paul de Vrieze
2005-09-16 18:14 ` Martin Schlemmer
2005-09-16 18:18 ` Brian Harring
2005-09-16 18:19 ` Simon Stelling
2005-09-16 18:38 ` Ciaran McCreesh
2005-09-16 18:48 ` Paul de Vrieze
2005-09-16 19:00 ` Daniel Ostrow
2005-09-17 9:28 ` Kevin F. Quinn
2005-09-17 9:34 ` Brian Harring
2005-09-17 12:02 ` Kevin F. Quinn
2005-09-17 20:17 ` Mike Frysinger
2005-09-17 21:59 ` Alec Warner
2005-09-17 22:45 ` Mike Frysinger
2005-09-18 6:46 ` Wernfried Haas [this message]
2005-09-18 6:51 ` Wernfried Haas
2005-09-18 12:32 ` Ciaran McCreesh
2005-09-18 13:01 ` Wernfried Haas
2005-09-18 14:05 ` Alec Warner
2005-09-19 1:58 ` Philip Webb
2005-09-18 15:38 ` Ciaran McCreesh
2005-09-18 12:40 ` Matti Bickel
2005-09-26 4:01 ` Andrew Muraco
2005-09-26 4:15 ` Mike Frysinger
2005-09-28 2:53 ` Marius Mauch
2005-09-16 19:02 ` Ciaran McCreesh
2005-09-16 19:12 ` Simon Stelling
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:46 ` Simon Stelling
2005-09-16 19:15 ` Mike Frysinger
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:11 ` Paul de Vrieze
2005-09-16 20:21 ` Aron Griffis
2005-09-16 20:25 ` Daniel Ostrow
2005-09-16 20:43 ` Mike Frysinger
2005-09-16 21:50 ` Mike Frysinger
2005-09-16 22:00 ` Kito
2005-09-16 22:23 ` Maurice van der Pot
2005-09-16 22:45 ` Carsten Lohrke
2005-09-16 23:14 ` Mike Frysinger
2005-09-16 20:37 ` Olivier Crete
2005-09-16 20:17 ` Carsten Lohrke
2005-09-16 20:38 ` Ciaran McCreesh
2005-09-16 21:23 ` Carsten Lohrke
2005-09-16 21:34 ` Ciaran McCreesh
2005-09-16 21:41 ` Patrick Lauer
2005-09-16 21:46 ` Ciaran McCreesh
2005-09-16 22:43 ` Carsten Lohrke
2005-09-16 23:00 ` Ciaran McCreesh
2005-09-16 23:19 ` Carsten Lohrke
2005-09-16 20:33 ` Mike Frysinger
2005-09-16 20:44 ` Ciaran McCreesh
2005-09-16 20:59 ` Mike Frysinger
2005-09-16 21:10 ` Ciaran McCreesh
2005-09-16 21:20 ` Simon Stelling
2005-09-16 21:26 ` Ciaran McCreesh
2005-09-16 21:51 ` Mike Frysinger
2005-09-19 9:32 ` Paul de Vrieze
2005-09-16 22:48 ` Carsten Lohrke
2005-09-16 21:57 ` Martin Schlemmer
2005-09-16 22:17 ` Mike Frysinger
2005-09-24 13:44 ` [gentoo-dev] " Duncan
2005-09-16 22:51 ` [gentoo-dev] " Carsten Lohrke
2005-09-16 20:16 ` Aron Griffis
2005-09-17 6:39 ` Elfyn McBratney
2005-09-15 23:47 ` Jason Stubbs
2005-09-24 13:21 ` [gentoo-dev] " Duncan
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=20050918064637.GB18094@superlupo.rechner \
--to=amne@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