public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Lawles <jl.050877@gmail.com>
To: Richard Freeman <rich0@gentoo.org>
Cc: Alec Warner <antarus@gentoo.org>, gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Plan, then communicate
Date: Mon, 21 Jan 2008 20:45:40 -0800	[thread overview]
Message-ID: <20080122044540.GA11340@redwoodscientific.com> (raw)
In-Reply-To: <4795580D.9090602@gentoo.org>

On Mon, Jan 21, 2008 at 09:42:21PM -0500, Richard Freeman wrote:
> how will a separate portage tree for devs be any different from
> what we already have (masking and keywording),

     Those don't help when it is the 'stable' part of the tree that
breaks.  The most exasperating problems that I can remember
involved basic libraries that were changed (upgraded or removed) in
the "stable" tree and that change, in turn, exposed broken
dependencies or some such elsewhere.  IIRC, libexpat was an example
of that and you can see the level of end-user frustration in a
thread such as:
http://forums.gentoo.org/viewtopic-t-575655-highlight-libexpat.html

> and how will we prevent users getting hit with even worse bugs
> because nobody is bothering to test anything in the environment
> that end-users actually use?

     The concept is that there would be a separate team maintaining
the stable tree.  A precedent for this would be the Linux kernel's
two-track development.

     I use my own mini-two-tree system.  I emerge --sync and then
wait a week.  During that week, many users will encounter bugs and
work-arounds start appearing in the forums.  After that week, I
upgrade in relative confidence that, while my system may break,
there is a good chance that there will be a known procedure for
fixing it.

     As a mere end-user, I am not recommending any particular
solution.  I am suggesting that more effort be devoted to
(a) recognizing user frustrations, (b) proposing good solutions,
and (c) letting us know that you see the problems and that
solutions are being worked on.

Regards,

John

P.S.
> What I recommend is running the stable tree in general, and then accepting 
> only individual packages in ~arch

Yes, that is what I do.  I would run completely stable but many
system essentials (such as, at my last upgrade, the X11 fonts) are
masked.

P.P.S. Again, my thanks to all developers for their monumental
efforts in making the distribution that I want to use.

-- 
gentoo-project@lists.gentoo.org mailing list



  reply	other threads:[~2008-01-22  4:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080120215706.GA16357@redwoodscientific.com>
     [not found] ` <b41005390801201455w241b8832wcc77da934c4edfb7@mail.gmail.com>
     [not found]   ` <20080120233809.GA18052@redwoodscientific.com>
     [not found]     ` <200801201908.07265.vapier@gentoo.org>
     [not found]       ` <20080121015439.GA18636@redwoodscientific.com>
2008-01-21  3:32         ` [gentoo-project] Re: Plan, then communicate (no-list) Alec Warner
2008-01-21  8:17           ` Graham Murray
2008-01-21  9:15             ` Marius Mauch
2008-01-21  9:23             ` Robin H. Johnson
2008-01-21 18:19           ` Steve Long
2008-01-21 18:27             ` Donnie Berkholz
2008-01-21 18:37             ` Richard Freeman
2008-01-23 13:48               ` [gentoo-project] " Steve Long
2008-01-23 18:42                 ` Donnie Berkholz
2008-01-23 18:37               ` [gentoo-project] " Donnie Berkholz
2008-01-21 19:18             ` Wulf C. Krueger
2008-01-23 13:53               ` [gentoo-project] " Steve Long
2008-01-23 14:50                 ` Nirbheek Chauhan
2008-01-23 16:37                   ` [gentoo-project] " Steve Long
2008-01-23 16:36                     ` Dale
2008-01-23 17:36                     ` Nirbheek Chauhan
2008-01-23 20:44                       ` [gentoo-project] " Steve Long
2008-01-23 15:15                 ` [gentoo-project] " Wulf C. Krueger
2008-01-23 16:44                   ` [gentoo-project] " Steve Long
2008-01-23 17:13                     ` Wulf C. Krueger
2008-01-23 19:44                       ` [gentoo-project] " Steve Long
2008-01-22 21:26             ` [gentoo-project] " Roy Bamford
2008-01-23 17:30               ` [gentoo-project] " Steve Long
2008-01-21 19:31           ` [gentoo-project] Re: Plan, then communicate John Lawles
2008-01-22  2:42             ` Richard Freeman
2008-01-22  4:45               ` John Lawles [this message]
2008-01-22 17:13                 ` Richard Freeman
2008-01-22 20:19                   ` Petteri Räty
2008-01-23 13:07                   ` [gentoo-project] " Steve Long
2008-01-24 15:59             ` [gentoo-project] " Joanet
2008-01-21 21:43           ` [gentoo-project] Re: Plan, then communicate (no-list) George Prowse
2008-01-22 21:18           ` [gentoo-project] Re: Plan, then communicate John Lawles
2008-01-22 23:58             ` Roy Bamford

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=20080122044540.GA11340@redwoodscientific.com \
    --to=jl.050877@gmail.com \
    --cc=antarus@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=rich0@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