From: "Paul Rolland" <rol@as2917.net>
To: "'Simon Oosthoek'" <simon@cal003100.student.utwente.nl>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x release process comments
Date: Thu, 20 Feb 2003 14:11:46 +0100 [thread overview]
Message-ID: <026601c2d8e1$9f2616f0$3f00a8c0@witbe> (raw)
In-Reply-To: <20030220125808.GA11694@margo.student.utwente.nl>
Hello,
> I'm not saying it should, but it would be good from a PR
> perspective and as
> an element in the reliability feeling vector ;-)
Not sure about it... People like it when a product looks stable,
and having a -blah or -pre and so on once a week doesn't make
me feel I have some stable product...
> The number of -pre releases shouldn't be limited for its own sake, but
> rather in the process of stabilising the kernel for release.
> So I mean after
> a couple of -pre releases start focussing on debugging and
> then finish with
> a few -rc's before the next cycle starts. That way the diffs
> between full
> versions are smaller and upgrading gets easier.
So, the question is to choose between :
- less releases with more changes
or
- more relaseases with less changes
Is that correct ?
Paul
next prev parent reply other threads:[~2003-02-20 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 10:24 2.4.x release process comments Simon Oosthoek
2003-02-20 10:56 ` John Bradford
2003-02-20 12:58 ` Simon Oosthoek
2003-02-20 13:11 ` Paul Rolland [this message]
2003-02-20 13:24 ` Simon Oosthoek
2003-02-20 14:51 ` Alan Cox
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='026601c2d8e1$9f2616f0$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@cal003100.student.utwente.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.