From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Some ideas on how to reduce territoriality
Date: Tue, 07 Aug 2007 04:48:09 +0100 [thread overview]
Message-ID: <f98q0l$mn2$1@sea.gmane.org> (raw)
In-Reply-To: 1186427782.8562.2.camel@inertia.twi-31o2.org
Chris Gianelloni wrote:
>> The stabilization idea sounds good and it could free maintainers from
>> filing similar bugs over and over ; but wouldn't this be more and harder
>> work for arch teams?. For example, they should carefully track the
>> history of all the packages to know when and if they should stabilize it
>> yet.
>
> Huh?
>
> It's simple. The maintainer says "stabilize foo-1.2-r1" which gives a
> minimum level that all arches should be using. If foo-1.2-r2 comes out,
> it is up to the arch team to decide if/when to stabilize it, *unless*
> the maintainer requests a newer version/revision. Basically, the
> maintainer sets the minimum level they would like stable.
>
Yeah, but is there no way for whatever the maintainer stabilises on their
arch to be what everyone else should stabilise, without "filing similar
bugs over and over"? (ie automation of this bit.)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-08-07 3:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:06 [gentoo-dev] Some ideas on how to reduce territoriality Chris Gianelloni
2007-08-03 22:19 ` Mike Doty
2007-08-03 22:47 ` Chris Gianelloni
2007-08-04 7:21 ` Marius Mauch
2007-08-03 22:23 ` Philipp Riegger
2007-08-03 22:34 ` Petteri Räty
2007-08-03 22:40 ` Donnie Berkholz
2007-08-03 23:03 ` Mike Doty
2007-08-03 23:06 ` Mike Doty
2007-08-03 23:20 ` Robin H. Johnson
2007-08-04 14:43 ` [gentoo-dev] Commitlog-mailinglist (was: Re: Some ideas on how to reduce territoriality) Lars Weiler
2007-08-04 19:32 ` [gentoo-dev] Commitlog-mailinglist Donnie Berkholz
2007-08-06 9:41 ` [gentoo-dev] Commitlog-mailinglist Christian Faulhammer
2007-08-06 12:23 ` [gentoo-dev] Commitlog-mailinglist (was: Re: Some ideas on how to reduce territoriality) Mike Frysinger
2007-08-06 14:43 ` [gentoo-dev] Commitlog-mailinglist Lars Weiler
2007-08-06 15:01 ` Ned Ludd
2007-08-06 15:48 ` Lars Weiler
2007-08-06 16:20 ` Petteri Räty
2007-08-03 22:43 ` [gentoo-dev] Some ideas on how to reduce territoriality Philipp Riegger
2007-08-03 22:23 ` Petteri Räty
2007-08-03 22:49 ` Chris Gianelloni
2007-08-04 7:36 ` Marius Mauch
2007-08-03 22:53 ` Roy Marples
2007-08-04 1:13 ` Luis Francisco Araujo
2007-08-06 19:16 ` Chris Gianelloni
2007-08-07 3:48 ` Steve Long [this message]
2007-08-04 9:06 ` Alec Warner
2007-08-04 16:29 ` [gentoo-dev] " Steve Long
2007-08-04 17:17 ` Martin Jackson
2007-08-04 17:27 ` [gentoo-dev] " Jeroen Roovers
2007-08-04 17:39 ` Vlastimil Babka
2007-08-04 17:56 ` Steev Klimaszewski
2007-08-04 20:05 ` Petteri Räty
2007-08-04 23:56 ` Jurek Bartuszek
2007-08-05 6:27 ` Jeroen Roovers
2007-08-06 12:26 ` Mike Frysinger
2007-08-06 16:18 ` Petteri Räty
2007-08-07 0:23 ` Mike Frysinger
2007-08-05 0:03 ` [gentoo-dev] " Steve Long
2007-08-05 7:50 ` Petteri Räty
2007-08-04 19:34 ` Tiziano Müller
2007-08-05 0:19 ` Steve Long
2007-08-05 16:14 ` [gentoo-dev] " Ciaran McCreesh
2007-08-06 14:09 ` [gentoo-dev] " Steve Long
2007-08-06 9:24 ` Christian Faulhammer
2007-08-06 11:16 ` [gentoo-dev] " Paul de Vrieze
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='f98q0l$mn2$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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