Mailing List Archive

"Legacy Free" apache-2.0 docs
Question: Should we remove all "compatibility" references in Apache 2.0
for earlier versions.

My opinion is that there should be a good "new features" document to help
people upgrade from 1.3, but other than that, there should be no
references to versions earlier than 2.0 in the docs. Those references are
not really there for people upgrading, but rather are for people who are
using earlier versions of apache with a later version of the docs. I
don't think there is any reason to expect that people using apache 1.3 (
or apache 1.2 or 1.1) will be looking for help in the 2.0 docs.

A few of the docs have actually become a nightmare of "If the version is
between 1.3.2 and 1.3.6 then X, otherwise if the version is between ...."

--
Joshua Slive
slive@finance.commerce.ubc.ca
http://finance.commerce.ubc.ca/~slive/
Phone: (604) 822-1871
Re: "Legacy Free" apache-2.0 docs [ In reply to ]
Joshua Slive <slive@finance.commerce.ubc.ca> wrote:
>
>My opinion is that there should be a good "new features" document to help
>people upgrade from 1.3, but other than that, there should be no
>references to versions earlier than 2.0 in the docs. Those references are
>not really there for people upgrading, but rather are for people who are
>using earlier versions of apache with a later version of the docs. I
>don't think there is any reason to expect that people using apache 1.3 (
>or apache 1.2 or 1.1) will be looking for help in the 2.0 docs.

They will be using the web site for reference, though. There is a
separate copy of the 1.2 docs there for that reason, and I expect us
to do the same for 1.3 in due course. Therefore I think it is OK to
remove references to pre-2.0 versions from the 2.0 docs.

>A few of the docs have actually become a nightmare of "If the version is
>between 1.3.2 and 1.3.6 then X, otherwise if the version is between ...."

However I don't think it is possible to avoid doing this for 2.0.1,
2.0.2 etc., at least not without maintining separate docs for release
tarballs and for the web site.

Tony.
--
en oeccget g mtcaa f.a.n.finch
v spdlkishrhtewe y dot@dotat.at
eatp o v eiti i d. fanf@covalent.net
Re: "Legacy Free" apache-2.0 docs [ In reply to ]
On Wed, 13 Sep 2000, Joshua Slive wrote:

> Question: Should we remove all "compatibility" references in Apache 2.0
> for earlier versions.

Sounds good to me.

Apache 2.0 docs should assume 2.0 and no less. A lot of keywords and
such will be changed anyway.

- ask

--
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 70M impressions per day, <http://valueclick.com>
Re: "Legacy Free" apache-2.0 docs [ In reply to ]
On Thu, 14 Sep 2000, Tony Finch wrote:

[...]
> They will be using the web site for reference, though. There is a
> separate copy of the 1.2 docs there for that reason, and I expect us
> to do the same for 1.3 in due course. Therefore I think it is OK to
> remove references to pre-2.0 versions from the 2.0 docs.

I agree. (that was what I assumed was the intention when I wrote the
previous mail).

> >A few of the docs have actually become a nightmare of "If the version is
> >between 1.3.2 and 1.3.6 then X, otherwise if the version is between ...."
>
> However I don't think it is possible to avoid doing this for 2.0.1,
> 2.0.2 etc., at least not without maintining separate docs for release
> tarballs and for the web site.

It should be done for 2.0.1 etc, just not for both 1.x and 2.x in
the same docs.

- ask

--
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 70M impressions per day, <http://valueclick.com>
Re: "Legacy Free" apache-2.0 docs [ In reply to ]
Joshua Slive wrote:
>
> My opinion is that there should be a good "new features" document
> to help people upgrade from 1.3, but other than that, there should
> be no references to versions earlier than 2.0 in the docs.

Works for me. +1.
--
#ken P-)}

Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>