From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: When will KDE 3.5 be marked as stable?
Date: Thu, 4 May 2006 15:45:02 +0200 [thread overview]
Message-ID: <200605041545.02549.pauldv@gentoo.org> (raw)
In-Reply-To: <8a0028260605040521y768be337w63e3f4689b7500f2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On Thursday 04 May 2006 14:21, Jeff Rollin wrote:
> All,
>
> If I might weigh in at this late stage:
>
> How did we end up here in the first place? Isn't the point of ~arch
> that we can put stuff here that might WELL be unstable? Sure, we'll get
> lots of "I set my ACCEPT_KEYWORDS to ~arch and now my system is
> broken," messages, but if people are going to try ~arch, or Gentoo in
> general, despite warnings that it's "not for newbies" (and I have
> personal experience of this), we can't really stop them without turning
> the community into a fascist state, can we? Gentoo (like all projects)
> has a finite amount of developers, and if we spend to much time on
> ~arch then surely arch will suffer
Actually the testing keywords are not for unstable packages. If something
is unstable it must be masked. If we however want to test our packaging
we put it in ~arch. If something is in ~arch that means that it works for
the packager, but that your mileage may vary. ~arch may sometimes have
unexpected problems, especially involving migration from old versions to
new versions. Actually most time is spent on ~arch, as there is where
development happens. As a package is seen to be stable, then it gets
promoted to arch. This is just a change of the keyword. The developer
then goes on to newer versions of the package.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]
next prev parent reply other threads:[~2006-05-04 13:50 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 23:05 [gentoo-dev] When will KDE 3.5 be marked as stable? m h
2006-04-03 23:11 ` Stephen P. Becker
2006-04-03 23:44 ` Aron Griffis
2006-04-04 2:16 ` Kari Hazzard
2006-04-04 2:28 ` Stephen P. Becker
2006-04-04 2:50 ` lnxg33k
2006-04-04 3:23 ` Jason S
2006-04-04 3:37 ` Kari Hazzard
2006-04-04 15:12 ` Stephen P. Becker
2006-04-04 16:11 ` Kari Hazzard
2006-04-04 16:37 ` Stephen P. Becker
2006-04-04 17:04 ` m h
2006-04-04 17:42 ` Phil Richards
2006-04-04 21:05 ` Paul de Vrieze
2006-04-04 21:09 ` Paul de Vrieze
2006-04-04 20:55 ` Paul de Vrieze
2006-04-04 16:42 ` Simon Stelling
2006-04-04 20:52 ` Paul de Vrieze
2006-04-04 2:37 ` Grant Goodyear
2006-04-04 12:05 ` Carsten Lohrke
2006-04-04 9:21 ` Michael Cummings
2006-04-04 9:42 ` Jan Kundrát
2006-04-04 10:38 ` Michael Cummings
2006-04-03 23:13 ` Diego 'Flameeyes' Pettenò
2006-04-03 23:25 ` m h
2006-04-04 5:51 ` [gentoo-dev] " Duncan
2006-04-04 6:16 ` Donnie Berkholz
2006-04-04 10:10 ` [gentoo-dev] " Duncan
2006-04-04 6:09 ` [gentoo-dev] " Philip Webb
2006-04-04 6:42 ` Diego 'Flameeyes' Pettenò
2006-04-04 10:28 ` [gentoo-dev] " Duncan
2006-04-04 12:03 ` [gentoo-dev] " Philip Webb
2006-04-04 9:12 ` Chris Bainbridge
2006-04-04 9:51 ` Diego 'Flameeyes' Pettenò
2006-04-04 10:14 ` [gentoo-dev] " Duncan
2006-04-04 10:38 ` Caleb Tennis
2006-04-04 11:17 ` [gentoo-dev] " Duncan
2006-04-04 12:18 ` [gentoo-dev] " Philip Webb
2006-05-04 11:48 ` [gentoo-dev] " Bart Braem
2006-05-04 12:18 ` Chris Gianelloni
2006-05-04 12:30 ` Jeff Rollin
2006-05-05 7:14 ` Philip Webb
2006-05-05 7:35 ` Jakub Moc
2006-05-05 7:56 ` Philip Webb
2006-05-05 8:11 ` Jakub Moc
2006-05-05 9:03 ` Michael Kirkland
2006-05-05 8:16 ` Chris Bainbridge
2006-05-05 20:09 ` Jeff Smelser
2006-05-06 9:03 ` Richard Fish
2006-05-04 12:21 ` Jeff Rollin
2006-05-04 13:45 ` Paul de Vrieze [this message]
2006-05-04 14:28 ` Jeff Rollin
2006-05-04 23:29 ` Michael Kirkland
2006-05-05 5:28 ` Jeff Rollin
2006-05-05 10:30 ` [gentoo-dev] " Duncan
2006-05-05 6:32 ` [gentoo-dev] " Kevin F. Quinn (Gentoo)
2006-05-05 11:20 ` Carsten Lohrke
2006-05-05 13:23 ` Kevin F. Quinn (Gentoo)
2006-05-05 14:38 ` Carsten Lohrke
2006-05-05 18:37 ` Kevin F. Quinn (Gentoo)
2006-05-05 19:10 ` Carsten Lohrke
2006-05-05 19:08 ` Chris Gianelloni
2006-05-05 7:20 ` [gentoo-dev] " Bart Braem
2006-05-05 8:03 ` Harald van Dijk
2006-05-05 8:33 ` Donnie Berkholz
2006-05-05 8:43 ` [gentoo-dev] " Bart Braem
2006-05-05 11:28 ` Duncan
2006-05-05 8:57 ` [gentoo-dev] " Patrick Lauer
2006-05-05 9:44 ` Diego 'Flameeyes' Pettenò
2006-05-06 6:48 ` Philip Webb
2006-05-06 11:41 ` Diego 'Flameeyes' Pettenò
2006-05-06 12:48 ` Philip Webb
2006-05-06 13:01 ` Jakub Moc
2006-05-06 13:18 ` [gentoo-dev] " Duncan
2006-05-05 10:50 ` [gentoo-dev] " Caleb Tennis
2006-05-05 11:27 ` [gentoo-dev] " Bart Braem
2006-05-05 11:19 ` [gentoo-dev] " Carsten Lohrke
2006-05-05 11:50 ` [gentoo-dev] " Bart Braem
2006-05-06 9:28 ` [gentoo-dev] " Richard Fish
2006-05-05 7:37 ` [gentoo-dev] " Philip Webb
2006-05-05 11:00 ` [gentoo-dev] " Duncan
2006-05-05 21:52 ` [gentoo-dev] " Jan Kundrát
2006-05-05 12:03 ` Marius Mauch
2006-05-04 13:05 ` Duncan
2006-05-04 13:47 ` Guillaume Pujol
2006-05-06 8:56 ` Richard Fish
2006-04-04 11:50 ` [gentoo-dev] " Carsten Lohrke
2006-04-08 13:41 ` Wernfried Haas
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=200605041545.02549.pauldv@gentoo.org \
--to=pauldv@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