From: Willy Tarreau <w@1wt.eu>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Marcelo Tosatti <marcelo@hera.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.33 released
Date: Fri, 11 Aug 2006 21:09:23 +0200 [thread overview]
Message-ID: <20060811190923.GJ8776@1wt.eu> (raw)
In-Reply-To: <1155318180.23933.7.camel@localhost>
Hello,
On Fri, Aug 11, 2006 at 07:43:00PM +0200, Kasper Sandberg wrote:
> On Fri, 2006-08-11 at 04:18 +0000, Marcelo Tosatti wrote:
> > final:
> >
> > - 2.4.33-rc3 was released as 2.4.33 with no changes.
> I have one suggestion for the 2.4 tree, next time a few changes is
> introduced, they could be put as a bugfix release, as with the 2.6
> branch now, so that it doesent end up taking years for a new 2.4
> release, and instead a point release(if any such thing happens at all)
This has already the case with the hotfix tree since 18 months or so. A
hotfix release is issued when there are important fixes. Anyway, I was
thinking about releasing pre-releases more often. Also, you might have
noticed that the slowdown is more important during -rc for obvious reasons.
To solve this problem, I intend to maintain a 'next' branch in the tree
which will contain the fixes that can wait for next version. It should
help us batch the fixes and reduce the latency between important fixes
and the associated release.
Regards,
Willy
next prev parent reply other threads:[~2006-08-11 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 4:18 linux-2.4.33 released Marcelo Tosatti
2006-08-11 17:43 ` Kasper Sandberg
2006-08-11 19:09 ` Willy Tarreau [this message]
2006-08-12 2:18 ` Grant Coady
2006-08-12 4:04 ` Willy Tarreau
2006-08-12 7:08 ` Grant Coady
2006-08-14 7:12 ` Arjan van de Ven
2006-08-14 7:30 ` Willy Tarreau
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=20060811190923.GJ8776@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=marcelo@hera.kernel.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