On Thu, 5 Aug 1999, Gilles Detillieux wrote:
> What about the linux kernel? I don't think we need to go quite that far,
> but for me it makes sense to maintain the stable release at least until
> the second beta of the next release is out, the assumption being that
I wasn't implying that we not maintain the stable release. I don't think
we should make any statement about upgrading until we firm up an actual
3.2.0 release.
I was referring to maintaing a "stable patch" repository. The Linux kernel
has "prepatches" but since they don't worry about announcements, they can
roll releases much more easily. Apache supposedly has a "patches-to-1.3.x"
archive, but it rarely contains anything.
> likely quite buggy. Right now, we don't even have the first beta out,
> so I see 3.1.2 as still very much alive and in need of support.
Very much so. I think I'd word an announcement for 3.2.0b1 *very*
carefully. People obviously want many of the features in this release, but
the current state of the code is a bit rough. I could forsee situations
like the 3.1.0bX series, where people might have to kill their existing
databases to properly upgrade because we find bugs in the database code.
> That would help, but I still find patches easiest to deal with, particularly
> since RPM deals with them so well.
True. I certainly think it's a good idea--it will make it easier to
respond to FAQs.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
