public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "brett holcomb" <brettholcomb@charter.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Three teir portage: stable, prestable, unstable?
Date: Tue, 07 Oct 2003 14:10:34 -0400	[thread overview]
Message-ID: <web-6105318@rems08.cluster1.charter.net> (raw)
In-Reply-To: <1065552596.4139.63.camel@Interimo.Intern.LAN>

What's wrong with the alpha beta being part of ~arch?  If 
someone is working with alpha/beta stuff they know what 
they're looking for?  I really don't see a need to have a 
multi-tier mess to keep track of alpha/beta/gamma stuff. 
 If it's arch it is stable and works.  If it's ~arch it 
may be broken and break your system.  When the developer 
deems it's okay it moves to arch.


On Tue, 07 Oct 2003 19:49:56 +0100
  Ian Leitch <port001@gentoo.org> wrote:
>On Tue, 2003-10-07 at 15:30, foser wrote:
>> I think the the problem is uninformedness about the 
>>policy, does it even
>> get properly read by new devs ? They assume they can do 
>>it because they
>> see another dev do it and so it spreads, you don't solve 
>>these problems
>> by accommodating them. 
>
>OK, so say something was done and from now on all devs 
>only submited
>packages to ~arch that they deemed stable but whos ebuild 
>could do with
>some more testing. Where does that leave the beta and 
>alpha software
>that a lot of Gentoo users love so much (myself 
>included)? Places like
>BreakMyGentoo would only become bigger and more breakage 
>would incur
>from the lack of QA. If we had an unstable branch, devs 
>would be able to
>keep up Gentoo's repretation of being a bleeding edge 
>meta-distribution.
>At the same time we could offer alpha gnome releases 
>within our control.
>Ofcourse a plan to combat the extra pointless bug reports 
>would need to
>be thought about, but I see that as a small side effect 
>compared to the
>benefits. 
>
>Regards,
>Ian.  
>
>
>--
>gentoo-dev@gentoo.org mailing list
>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-10-07 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 21:47 [gentoo-dev] Three teir portage: stable, prestable, unstable? Ian Leitch
2003-10-06 20:51 ` Lisa Seelye
2003-10-06 22:08   ` Ian Leitch
2003-10-06 22:08     ` foser
2003-10-07  9:46       ` Paul de Vrieze
2003-10-07 12:07         ` foser
2003-10-07 13:04           ` Paul de Vrieze
2003-10-07 14:30             ` foser
2003-10-07 18:49               ` Ian Leitch
2003-10-07 18:10                 ` brett holcomb [this message]
2003-10-07 18:27                   ` Paul de Vrieze
2003-10-07 21:57                     ` Jason Stubbs
2003-10-07 21:41                 ` foser
2003-10-06 21:00 ` Stuart Herbert
2003-10-06 21:22 ` Mike Frysinger
2003-10-06 21:56 ` Sven Blumenstein

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=web-6105318@rems08.cluster1.charter.net \
    --to=brettholcomb@charter.net \
    --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