You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Justin Erenkrantz <ju...@erenkrantz.com> on 2004/11/07 22:29:30 UTC
Re: cvs commit: httpd-2.0/docs/manual new_features_2_2.html
new_features_2_2.html.en new_features_2_2.xml
new_features_2_2.xml.meta
> * pquerna@apache.org wrote:
>
>> pquerna 2004/11/06 22:01:50
>>
>> Added: docs/manual new_features_2_2.html
>> new_features_2_2.html.en
>> new_features_2_2.xml new_features_2_2.xml.meta
>> Log:
>> First Swing at a 2.0 -> 2.2 New Features Document.
>
> As long as we just have 2.1, wouldn't it be better to have a
> new_features_2_1
> document? We use the 2.1 version number all over the docs.
> (and I don't see 2.2 tomorrow ;)
IMHO, no. 2.1 will never be a 'public' release by our versioning
definition. Only 2.2 will be something that we'd recommend to the general
public. 2.1 could only be at best beta. -- justin
Re: cvs commit: httpd-2.0/docs/manual new_features_2_2.html
new_features_2_2.html.en new_features_2_2.xml
new_features_2_2.xml.meta
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
At 04:49 PM 11/7/2004, André Malo wrote:
>* "Justin Erenkrantz" <ju...@erenkrantz.com> wrote:
>
>
>Well, but it's still the 2.1 branch with 2.1 docs (docs-2.1/). And, of course,
>once tagged and released (as alpha, beta, whatever) it *is* public. Though not
>stable. That's a difference :)
That's your issue right there - no reason for a 2.1 docs tree :)
It should be the 2.2 docs tree (with something in the 2.1 tarballs
telling users that's the future version of this code.) Once all the
changes to HEAD are done for httpd-docs-2.0, it will branch, and new
work on the 2.3 dev will be sent again to cvs HEAD until 2.4 (or 3.0)
goes out the door.
To make things clearer, any textual context for the different docs
flavors should indicate 'Apache 2.2 future release (2.1 development)'.
2.1 is entirely developer/beta oriented.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: cvs commit: httpd-2.0/docs/manual new_features_2_2.html
new_features_2_2.html.en new_features_2_2.xml
new_features_2_2.xml.meta
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
At 04:49 PM 11/7/2004, André Malo wrote:
>* "Justin Erenkrantz" <ju...@erenkrantz.com> wrote:
>
>
>Well, but it's still the 2.1 branch with 2.1 docs (docs-2.1/). And, of course,
>once tagged and released (as alpha, beta, whatever) it *is* public. Though not
>stable. That's a difference :)
That's your issue right there - no reason for a 2.1 docs tree :)
It should be the 2.2 docs tree (with something in the 2.1 tarballs
telling users that's the future version of this code.) Once all the
changes to HEAD are done for httpd-docs-2.0, it will branch, and new
work on the 2.3 dev will be sent again to cvs HEAD until 2.4 (or 3.0)
goes out the door.
To make things clearer, any textual context for the different docs
flavors should indicate 'Apache 2.2 future release (2.1 development)'.
2.1 is entirely developer/beta oriented.
Bill
Re: cvs commit: httpd-2.0/docs/manual new_features_2_2.html
new_features_2_2.html.en new_features_2_2.xml
new_features_2_2.xml.meta
Posted by André Malo <nd...@perlig.de>.
* "Justin Erenkrantz" <ju...@erenkrantz.com> wrote:
> > * pquerna@apache.org wrote:
> >
> >> pquerna 2004/11/06 22:01:50
> >>
> >> Added: docs/manual new_features_2_2.html
> >> new_features_2_2.html.en
> >> new_features_2_2.xml new_features_2_2.xml.meta
> >> Log:
> >> First Swing at a 2.0 -> 2.2 New Features Document.
> >
> > As long as we just have 2.1, wouldn't it be better to have a
> > new_features_2_1
> > document? We use the 2.1 version number all over the docs.
> > (and I don't see 2.2 tomorrow ;)
>
> IMHO, no. 2.1 will never be a 'public' release by our versioning
> definition. Only 2.2 will be something that we'd recommend to the general
> public. 2.1 could only be at best beta. -- justin
Well, but it's still the 2.1 branch with 2.1 docs (docs-2.1/). And, of course,
once tagged and released (as alpha, beta, whatever) it *is* public. Though not
stable. That's a difference :)
nd
--
>>> Muschelflucht-Zusatzeinrichtung.
>> Shell-Escape ist ja noch klar, aber `Zusatzeinrichtung'?
> extension?
Feature. -- gefunden in de.org.ccc
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: cvs commit: httpd-2.0/docs/manual new_features_2_2.html
new_features_2_2.html.en new_features_2_2.xml
new_features_2_2.xml.meta
Posted by André Malo <nd...@perlig.de>.
* "Justin Erenkrantz" <ju...@erenkrantz.com> wrote:
> > * pquerna@apache.org wrote:
> >
> >> pquerna 2004/11/06 22:01:50
> >>
> >> Added: docs/manual new_features_2_2.html
> >> new_features_2_2.html.en
> >> new_features_2_2.xml new_features_2_2.xml.meta
> >> Log:
> >> First Swing at a 2.0 -> 2.2 New Features Document.
> >
> > As long as we just have 2.1, wouldn't it be better to have a
> > new_features_2_1
> > document? We use the 2.1 version number all over the docs.
> > (and I don't see 2.2 tomorrow ;)
>
> IMHO, no. 2.1 will never be a 'public' release by our versioning
> definition. Only 2.2 will be something that we'd recommend to the general
> public. 2.1 could only be at best beta. -- justin
Well, but it's still the 2.1 branch with 2.1 docs (docs-2.1/). And, of course,
once tagged and released (as alpha, beta, whatever) it *is* public. Though not
stable. That's a difference :)
nd
--
>>> Muschelflucht-Zusatzeinrichtung.
>> Shell-Escape ist ja noch klar, aber `Zusatzeinrichtung'?
> extension?
Feature. -- gefunden in de.org.ccc