> Because I value what little of my sanity remains, and am guarding it
> jealously. A 12-month release cycle for etch would mean that someone else
> would need to take point on it; the rate at which the release team's
> involvement would have to ramp up again for a 12-month cycle wouldn't leave
>
Il giorno ven, 10-06-2005 alle 18:58 -0700, Thomas Bushnell BSG ha
scritto:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > On Fri, Jun 10, 2005 at 11:14:02PM +0200, martin f krafft wrote:
> >> also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
> >> > Currently, I am planni
Steve Langasek wrote:
> Currently, I am planning to stick around for etch. If we're still waiting
> for etch two years from now, it's hard to predict how I'll feel at that
> point. :)
Ugh! However, that'd be still one year faster than sarge...
Regards,
Joey
--
Reading is a lost art n
On Fri, Jun 10, 2005 at 06:58:35PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > On Fri, Jun 10, 2005 at 11:14:02PM +0200, martin f krafft wrote:
> >> also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
> >> > Currently, I am planning to sti
On Thu, Jun 09, 2005 at 01:59:14PM +0200, Frederik Schueler wrote:
> please find attached a patch adding the amd64 architecture to the
> english release notes.
>
> These release notes are used for the unofficial debian-amd64 Sarge
> release.
>
> The patch only adds ifdeffed amd64 paragraphs but
On Fri, Jun 10, 2005 at 06:58:35PM -0700, Thomas Bushnell BSG wrote:
>
> Why not? The following seems like a reasonable plan to me:
>
> By the end of June, decide the release criteria.
>
> By the end of September, have the GCC changes in place and other
> infrastructural changes that we know we
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Fri, Jun 10, 2005 at 11:14:02PM +0200, martin f krafft wrote:
>> also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
>> > Currently, I am planning to stick around for etch. If we're still waiting
>> > for etch two years from now,
On Fri, Jun 10, 2005 at 11:14:02PM +0200, martin f krafft wrote:
> also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
> > Currently, I am planning to stick around for etch. If we're still waiting
> > for etch two years from now, it's hard to predict how I'll feel at that
> > p
also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
> Currently, I am planning to stick around for etch. If we're still waiting
> for etch two years from now, it's hard to predict how I'll feel at that
> point. :)
QUICK, ALL: this should be enough of a reason to get etch out i
On Thu, Jun 09, 2005 at 07:18:34AM +0200, Christian Perrier wrote:
> OK, I think that most if not all members of the Debian project will
> agree that our release team has been one of the major actors in the
> release of sarge.
> Actually, having a few people who take the responsibility of having
>
On Thu, Jun 09, 2005 at 03:29:41AM -0400, Joey Hess wrote:
> Christian Perrier wrote:
> > For this not to happen, we might need to have an already established
> > release team for etch. Maybe the people currently involved in the
> > release team as RM and assistant RM just want to continue the hard
Bring on the best software...at the most reasonable prices!
http://ajlr.wl0tzdept6w3bxw.goodingdn.com
Ah! the clock is always slow; It is later than you think.
Sure, winning isn't everything. It's the only thing.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
12 matches
Mail list logo
