According to Geoff Hutchison:
> On Wed, 4 Aug 1999, Gilles Detillieux wrote:
> > know that I want to have parallel releases (i.e. no 3.1.3), but an up to
> > date and tested patch collection would be useful. I will try to make sure
> > these bug fixes that aren't in 3.2 yet, or aren't quite right, will be
> > in the next couple weeks.
>
> I've been thinking about this too. I don't know of other projects that do
> this, but it seems to make sense to have a "patches to latest stable"
> directory for useful, if not necessarily critical patches.
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
the first beta will likely be too bleeding edge for a lot of users, and
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.
> They should obviously have sufficient READMEs, but I think it would solve
> a lot of problems (e.g. with the *_index.html bug) that didn't necessarily
> merit a full release.
Yes, most of the patches I've collected have a one or two line description,
and I'm putting together a summary as well.
> (Yes, I know, we should tighten up the steps for release so it isn't quite
> a big deal.)
That would help, but I still find patches easiest to deal with, particularly
since RPM deals with them so well.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
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.
