[OpenAFS-devel] Patch to implement default tuning proposal discussed a while ago

[Russ Allbery]

Niklas Edmundsson <Niklas.Edmundsson@hpc2n.umu.se> writes:
> On Tue, 16 Aug 2005, Russ Allbery wrote:

>> Oh, I'm sure it will!  That's just likely not a 1.4.0 thing, so I went
>> ahead and did something similar directly in the init script for the
>> Debian unstable packages so that we can get some early experience with
>> it.  I'm hoping to thereby get some evidence to back up including this
>> change into 1.4.1 or 1.4.2.

> Changes like this should be done in the development series, which is
> 1.3.x. When you get to stable, you don't want to surprise users by
> changing behaviour.

1.3.x is the development series for 1.4.  Nothing is going into the 1.3.x
releases that isn't also going to go into 1.4 (to do so would be very
confusing, since people upgrading from 1.3 to 1.4 would see features go
away).

These changes *could* be committed to the trunk right now, and if Jim
decides to do that, I certainly don't object.  In general, though, the
more stuff that's on the trunk that isn't targetted for 1.4, the more
there is to keep track of and the more complicated it is to be sure that
we got everything for the release.

I'm sitting on several patches that I plan to commit as soon as 1.4 is
released and it feels safer for the trunk to start diverging from the
stable release again.

>> There are no man pages; there are text documents that are formatted
>> vaguely like man pages but aren't really useful substitutes.  I have a
>> patch to start the process of converting the HTML documents to POD so
>> that we have man pages that we can really update.  This too is
>> something for after 1.4.0.

> I beg to differ. Proper documentation is a must in a stable release, I'd
> even say it's a release criteria. Todays situation of having a plethora
> of undocumented tuning options is most likely to annoy many users
> (including me).

1.4 has already been delayed for several months and needs to be released
as soon as we sort out the last few bugs.  There is absolutely no way that
I'm going to do major new work in 1.4 right now.  Sorry, you're just going
to have to live with that.

Many of these sorts of changes should be eligible for 1.4.1 or 1.4.2.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>