public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Olivier Crete <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 19: Gentoo Stable Portage Tree -- ideas
Date: Fri, 06 Jan 2006 18:11:51 -0500	[thread overview]
Message-ID: <1136589111.8876.40.camel@cocagne.max-t.internal> (raw)
In-Reply-To: <20060106173901.GF28075@nightcrawler.e-centre.net>

On Fri, 2006-06-01 at 09:39 -0800, Brian Harring wrote:
> On Fri, Jan 06, 2006 at 10:05:49AM -0500, Chris Gianelloni wrote:
> > On Fri, 2006-01-06 at 09:00 +0000, Chris Bainbridge wrote:
> > > On 06/01/06, Brian Harring <ferringb@gentoo.org> wrote:
> > > 1)  Manpower. There are already 10,000 open bugs in bugzilla (and
> > > growing) without adding more.
> > 
> > This is probably the primary reason it died.  This, of course, ties in
> > greatly to #2.
> 
> Automation can reduce workload, within limits.  Fex, scripting for 
> yanking packages/deptree out of normal tree for merging into a g19 
> tree.

Baz has developed a script that would yank a subtree with the proper
deps for the original GLEP 19 effort. It wasn't that hard to do.

And the idea of having a subtree is that the backports would be done by
a specific group of developers instead of the package maintainers and
therefore not getting any more work on the other devs.

I'm not really sure why the older one died... We were pretty close to
being able to build the stages and starting to distribute it... I would
be very favorable to seeing the whole thing restarted.

-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer


-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-01-06 23:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06  4:42 [gentoo-dev] GLEP 19: Gentoo Stable Portage Tree -- ideas Andrew Muraco
2006-01-06  4:52 ` Andrew Muraco
2006-01-06  5:29   ` Brian Harring
2006-01-06  5:35 ` Brian Harring
2006-01-06  9:00   ` Chris Bainbridge
2006-01-06  9:36     ` [gentoo-dev] " Duncan
2006-01-06 15:09       ` Chris Gianelloni
2006-01-06 15:27         ` Lance Albertson
2006-01-06 16:19           ` Carsten Lohrke
2006-01-06 18:59             ` Chris Gianelloni
2006-01-06 16:46           ` Grant Goodyear
2006-01-06 17:12             ` Grant Goodyear
2006-01-08  0:24             ` Stuart Herbert
2006-01-06 17:25           ` Brian Harring
2006-01-06 18:41           ` Donnie Berkholz
2006-01-06 18:57           ` Chris Gianelloni
2006-01-06 15:05     ` [gentoo-dev] " Chris Gianelloni
2006-01-06 17:39       ` Brian Harring
2006-01-06 19:30         ` Chris Gianelloni
2006-01-06 22:48           ` [gentoo-dev] " Duncan
2006-01-06 23:32             ` Lance Albertson
2006-01-08 14:14               ` Chris Gianelloni
2006-01-08 16:55                 ` Lance Albertson
2006-01-08 17:19                   ` Brian Harring
2006-01-08 17:26                     ` Lance Albertson
2006-01-06 23:11         ` Olivier Crete [this message]
2006-01-08 14:12           ` [gentoo-dev] " Chris Gianelloni

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=1136589111.8876.40.camel@cocagne.max-t.internal \
    --to=tester@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