You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@lnd.com> on 2000/07/03 17:38:14 UTC
FW: cvs commit: apache-1.3/src CHANGES
I think this wraps it... there are a few testers still bashing.
Would have polled again for votes, but having another handful of
apbugs duplicate reports in my inbox drove me over the edge :)
All we need is a "Win32 services were radically overhauled in
1.3.13, please download it and try to reproduce your problem" button.
I can't find a place to document --ntservice that won't confuse
the user. Since there are no suggestions, I've popped it from the
showstoppers queue. It's similar to the -Z opt, and that is also
undocumented since it doesn't apply to the user themselves.
If we can reach an agreement on the defaulted ServerName messages
(remembering the logs aren't opened when we find_fqdn() ) then we
should be ready to roll.
Arguments pro/con? Anything missing? Anyone want to choose a date?
Bill
> wrowe 00/07/03 08:24:25
>
> Modified: . STATUS
> src CHANGES
> Log:
> Bringing these up to date.
>
> Index: STATUS
> ===================================================================
> RELEASE SHOWSTOPPERS:
>
> - * Add a simple Win32 hold console open patch (wait for close or
> - the ESC key, with a nice message) if the server died a
> - bad death (non-zero exit code) in console mode.
> - OtherBill posted <00...@corecomm.net>
> - patch to address this and the NT service log to the list, and
> - is awaiting comments.
> -
> - * Document the --ntservice flag for Win32 (not a user option, only for
> - launching apache.exe from the WinNT service control manager).
> - OtherBill will do so.
> -
> * Resolve the status message that the ServerName has been overridden.
> Consensus says this should not appear to the user's console, but
> might be an appropriate information entry to log. The problem is
> that we resolve this before log files are open. Resolutions?
> + Jeff Tarwick is reviewing.
>
>
> Index: CHANGES
> ===================================================================
> Changes with Apache 1.3.13
>
> + *) Win32 NT and 2000 services now capture stderr messages that occur
> + before Apache's logs are opened to the Application Event Log.
> + Console and Win9x services now hold the console open for 30 seconds
> + (and may be dismissed with the <ESC> key) if they exit with an error.
> + [William Rowe]
> +
Re: FW: cvs commit: apache-1.3/src CHANGES
Posted by Eric Cholet <ch...@logilune.com>.
> Other than that, I'm cool with 1.3.13 soon.
Would be nice if my ap_configtestonly patch could be included,
the patch was reworked after being reviewed on this list.
(<00...@logilune.com>, let me know
if you want me to repost it).
Thanks,
--
Eric
Re: FW: cvs commit: apache-1.3/src CHANGES
Posted by Bill Stoddard <st...@raleigh.ibm.com>.
Let's not do this in 1.3. Save it for 2.0.
Bill
> "William A. Rowe, Jr." wrote:
> >
> > > Oh, and I'd like to do the docco split before rolling.
> > > (This week..)
> >
> > Hmmm... confused, which split are we refering to?
>
> Moving the docco out of the code tree into separate top-level
> CVS modules.
> --
> #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/>
RE: FW: cvs commit: apache-1.3/src CHANGES
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: Rodent of Unusual Size [mailto:Ken.Coar@Golux.Com]
> Sent: Wednesday, July 05, 2000 2:39 PM
>
> "William A. Rowe, Jr." wrote:
> >
> > I would add that the "This feature in version 1.3.7" junk aught
> > to all be killed off. 2.0 is 2.0, and I don't believe it's worth
> > it to walk the user through each revision. A note that the feature
> > is new in 2.0 is worthwhile for users trying to understand the new
> > server, but the blow by blow of 1.x is probably of little value.
>
> I disagree, since a lot of the mail I deal with is from people
> using 1.3.4, 1.3b3, and even 1.2.6. Those little notes can
> come out of the 2.0 docs, sure -- but they need to stay in
> the 1.3 stuff. And -1 right now on 'retiring' the 1.3 docs
> before we even have a 2.0 beta.
Very good - then I understand what we are doing here :) I still believe
that 2.0 should be a new doc set, but let's not split it till the docco
folks have 1.3.x clean and readable... there is a wealth of things moving
forward to 2.0 that need improvement in 1.3.x.
1.3.x will be around a very long time, and I agree that the less time we
waste answering goofy questions on the old version, the more attention
we can direct to the 2.0 development stream.
+1 on splitting docco of 1.3.x
> > They can always click to the 1.3.x archives to read the old docs.
>
> Heh. If they can find them.
Ok, standards for the 2.0 docset should state that every module should
have hotlinks to their 1.3 historical file, something like:
_Apache_ _Modules_ _All_Directives_ _Version_1.x_
That's a thought for building 2.0, although a forward reference would
be nice as well (_Version_2.x_)
I'm -0 on trying to keep one docset for both major versions.
> Look, *we* don't reference the documentation very much, and when
> we do we know where to look. I don't think it is appropriate for
> us to assume that we know how the users make use of it. Especially
> when we do have indications that they use it differently than
> we do.
> --
> #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/>
>
Re: FW: cvs commit: apache-1.3/src CHANGES
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
"William A. Rowe, Jr." wrote:
>
> I would add that the "This feature in version 1.3.7" junk aught
> to all be killed off. 2.0 is 2.0, and I don't believe it's worth
> it to walk the user through each revision. A note that the feature
> is new in 2.0 is worthwhile for users trying to understand the new
> server, but the blow by blow of 1.x is probably of little value.
I disagree, since a lot of the mail I deal with is from people
using 1.3.4, 1.3b3, and even 1.2.6. Those little notes can
come out of the 2.0 docs, sure -- but they need to stay in
the 1.3 stuff. And -1 right now on 'retiring' the 1.3 docs
before we even have a 2.0 beta.
> They can always click to the 1.3.x archives to read the old docs.
Heh. If they can find them.
Look, *we* don't reference the documentation very much, and when
we do we know where to look. I don't think it is appropriate for
us to assume that we know how the users make use of it. Especially
when we do have indications that they use it differently than
we do.
--
#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/>
RE: FW: cvs commit: apache-1.3/src CHANGES
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> From: William A. Rowe, Jr. [mailto:wrowe@lnd.com]
> Sent: Wednesday, July 05, 2000 1:56 PM
>
> Does that matter so much to 1.3.x, since that doc line is
> probably a dead horse after we roll 1.3.13? I was picturing
> the 2.0 docs growing their own cvs tree.
I would add that the "This feature in version 1.3.7" junk aught
to all be killed off. 2.0 is 2.0, and I don't believe it's worth
it to walk the user through each revision. A note that the feature
is new in 2.0 is worthwhile for users trying to understand the new
server, but the blow by blow of 1.x is probably of little value.
They can always click to the 1.3.x archives to read the old docs.
Bill
> > From: Rodent of Unusual Size [mailto:Ken.Coar@Golux.Com]
> > Sent: Wednesday, July 05, 2000 12:38 PM
> >
> > "William A. Rowe, Jr." wrote:
> > >
> > > > Oh, and I'd like to do the docco split before rolling.
> > > > (This week..)
> > >
> > > Hmmm... confused, which split are we refering to?
> >
> > Moving the docco out of the code tree into separate top-level
> > CVS modules.
> > --
> > #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/>
> >
>
RE: FW: cvs commit: apache-1.3/src CHANGES
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
Does that matter so much to 1.3.x, since that doc line is
probably a dead horse after we roll 1.3.13? I was picturing
the 2.0 docs growing their own cvs tree.
Bill
> From: Rodent of Unusual Size [mailto:Ken.Coar@Golux.Com]
> Sent: Wednesday, July 05, 2000 12:38 PM
>
> "William A. Rowe, Jr." wrote:
> >
> > > Oh, and I'd like to do the docco split before rolling.
> > > (This week..)
> >
> > Hmmm... confused, which split are we refering to?
>
> Moving the docco out of the code tree into separate top-level
> CVS modules.
> --
> #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/>
>
Re: FW: cvs commit: apache-1.3/src CHANGES
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
"William A. Rowe, Jr." wrote:
>
> > Oh, and I'd like to do the docco split before rolling.
> > (This week..)
>
> Hmmm... confused, which split are we refering to?
Moving the docco out of the code tree into separate top-level
CVS modules.
--
#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/>
RE: FW: cvs commit: apache-1.3/src CHANGES
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
> -----Original Message-----
> From: Rodent of Unusual Size [mailto:Ken.Coar@Golux.Com]
> Sent: Monday, July 03, 2000 4:57 PM
> To: new-httpd@apache.org
> Subject: Re: FW: cvs commit: apache-1.3/src CHANGES
>
>
> "William A. Rowe, Jr." wrote:
> >
> > Arguments pro/con? Anything missing? Anyone want to choose a date?
>
> I would like to get the remaining three Remove* (e.g., RemoveEncoding)
> items in so people don't get with the same problem we had with the
> .gz.asc files, but that will need a vote.
+1 - This bothers me too :)
> Oh, and I'd like to do the docco split before rolling.
> (This week..)
Hmmm... confused, which split are we refering to?
> Other than that, I'm cool with 1.3.13 soon.
> --
> #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/>
>
Re: FW: cvs commit: apache-1.3/src CHANGES
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
"William A. Rowe, Jr." wrote:
>
> Arguments pro/con? Anything missing? Anyone want to choose a date?
I would like to get the remaining three Remove* (e.g., RemoveEncoding)
items in so people don't get with the same problem we had with the
.gz.asc files, but that will need a vote. Oh, and I'd like to
do the docco split before rolling. (This week..)
Other than that, I'm cool with 1.3.13 soon.
--
#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/>
Re: cvs commit: apache-1.3/src CHANGES
Posted by David Reid <dr...@jetnet.co.uk>.
I'll repost the patch as the first one had an omission (that's what you get
for having difrferent trees and working too late!).
david
----- Original Message -----
From: "William A. Rowe, Jr." <wr...@lnd.com>
To: <ne...@apache.org>
Sent: Wednesday, July 12, 2000 3:33 PM
Subject: RE: cvs commit: apache-1.3/src CHANGES
>
> Does anyone else have an interest in releasing 1.3.13 and
> taking this off our plate? 2.0 general release won't roll till
> at least October, if then. I wouldn't even mind seeing 2.0-beta 1
> roll at ApacheCon Europe, as long as the users have something in
> their hands. Based on the state of discussions and the serious
> consideration all of the filter patchers are putting into their
> respective designs though, this won't be resolved instantly.
>
> I'm suggesting Friday. That gives us two days to decide for the
> defaulted ServerName where we will log it and what situations
> will be logged.
>
> My other question was never answered, is there someone who can roll
> the 1.3.13 binary Win32 release with the existing tools? With the
> hold console open patch, we don't need the batch file thunk, but we
> do need to clean up the shortcut names so they are less confusing.
>
> This would be the time to speak up if there are any late concerns,
> but regardless this should roll very, very soon.
>
> Bill
>
> Also, to David;
>
> > From: David Reid [mailto:dreid@jetnet.co.uk]
> > Sent: Tuesday, July 04, 2000 12:45 PM
> >
> > Can we get the changes for BeOS in?
>
> What's the status? Approved? And what code paths does it affect?
>
> I ask since if it affects the core, Roy has very serious reservations.
>
> I have no objections, but am in no position to test the changes.
>
> > From: "Bill Stoddard" <re...@attglobal.net>
> > To: <ne...@apache.org>
> >
> > > +1 on releasing next week.
> > >
> > > Bill
> > >
> > > > I think this wraps it... there are a few testers still bashing.
> > > >
> > > > Would have polled again for votes, but having another handful of
> > > > apbugs duplicate reports in my inbox drove me over the edge :)
> > > > All we need is a "Win32 services were radically overhauled in
> > > > 1.3.13, please download it and try to reproduce your
> > problem" button.
> > > >
> > > > I can't find a place to document --ntservice that won't confuse
> > > > the user. Since there are no suggestions, I've popped it from the
> > > > showstoppers queue. It's similar to the -Z opt, and that is also
> > > > undocumented since it doesn't apply to the user themselves.
> > > >
> > > > If we can reach an agreement on the defaulted ServerName messages
> > > > (remembering the logs aren't opened when we find_fqdn() ) then we
> > > > should be ready to roll.
> > > >
> > > > Arguments pro/con? Anything missing? Anyone want to
> > choose a date?
> > > >
> > > > Bill
> > > >
> > > > > wrowe 00/07/03 08:24:25
> > > > >
> > > > > Index: STATUS
> > > > >
===================================================================
> > > > > * Resolve the status message that the ServerName has been
overridden.
> > > > > Consensus says this should not appear to the user's
console, but
> > > > > might be an appropriate information entry to log. The
problem is
> > > > > that we resolve this before log files are open.
Resolutions?
> > > > > + Jeff Tarwick is reviewing.
>
>
RE: cvs commit: apache-1.3/src CHANGES
Posted by "William A. Rowe, Jr." <wr...@lnd.com>.
Does anyone else have an interest in releasing 1.3.13 and
taking this off our plate? 2.0 general release won't roll till
at least October, if then. I wouldn't even mind seeing 2.0-beta 1
roll at ApacheCon Europe, as long as the users have something in
their hands. Based on the state of discussions and the serious
consideration all of the filter patchers are putting into their
respective designs though, this won't be resolved instantly.
I'm suggesting Friday. That gives us two days to decide for the
defaulted ServerName where we will log it and what situations
will be logged.
My other question was never answered, is there someone who can roll
the 1.3.13 binary Win32 release with the existing tools? With the
hold console open patch, we don't need the batch file thunk, but we
do need to clean up the shortcut names so they are less confusing.
This would be the time to speak up if there are any late concerns,
but regardless this should roll very, very soon.
Bill
Also, to David;
> From: David Reid [mailto:dreid@jetnet.co.uk]
> Sent: Tuesday, July 04, 2000 12:45 PM
>
> Can we get the changes for BeOS in?
What's the status? Approved? And what code paths does it affect?
I ask since if it affects the core, Roy has very serious reservations.
I have no objections, but am in no position to test the changes.
> From: "Bill Stoddard" <re...@attglobal.net>
> To: <ne...@apache.org>
>
> > +1 on releasing next week.
> >
> > Bill
> >
> > > I think this wraps it... there are a few testers still bashing.
> > >
> > > Would have polled again for votes, but having another handful of
> > > apbugs duplicate reports in my inbox drove me over the edge :)
> > > All we need is a "Win32 services were radically overhauled in
> > > 1.3.13, please download it and try to reproduce your
> problem" button.
> > >
> > > I can't find a place to document --ntservice that won't confuse
> > > the user. Since there are no suggestions, I've popped it from the
> > > showstoppers queue. It's similar to the -Z opt, and that is also
> > > undocumented since it doesn't apply to the user themselves.
> > >
> > > If we can reach an agreement on the defaulted ServerName messages
> > > (remembering the logs aren't opened when we find_fqdn() ) then we
> > > should be ready to roll.
> > >
> > > Arguments pro/con? Anything missing? Anyone want to
> choose a date?
> > >
> > > Bill
> > >
> > > > wrowe 00/07/03 08:24:25
> > > >
> > > > Index: STATUS
> > > > ===================================================================
> > > > * Resolve the status message that the ServerName has been overridden.
> > > > Consensus says this should not appear to the user's console, but
> > > > might be an appropriate information entry to log. The problem is
> > > > that we resolve this before log files are open. Resolutions?
> > > > + Jeff Tarwick is reviewing.
Re: cvs commit: apache-1.3/src CHANGES
Posted by David Reid <dr...@jetnet.co.uk>.
Can we get the changes for BeOS in?
david
----- Original Message -----
From: "Bill Stoddard" <re...@attglobal.net>
To: <ne...@apache.org>
Sent: Tuesday, July 04, 2000 2:42 AM
Subject: Re: cvs commit: apache-1.3/src CHANGES
> +1 on releasing next week.
>
> Bill
>
> > I think this wraps it... there are a few testers still bashing.
> >
> > Would have polled again for votes, but having another handful of
> > apbugs duplicate reports in my inbox drove me over the edge :)
> > All we need is a "Win32 services were radically overhauled in
> > 1.3.13, please download it and try to reproduce your problem" button.
> >
> > I can't find a place to document --ntservice that won't confuse
> > the user. Since there are no suggestions, I've popped it from the
> > showstoppers queue. It's similar to the -Z opt, and that is also
> > undocumented since it doesn't apply to the user themselves.
> >
> > If we can reach an agreement on the defaulted ServerName messages
> > (remembering the logs aren't opened when we find_fqdn() ) then we
> > should be ready to roll.
> >
> > Arguments pro/con? Anything missing? Anyone want to choose a date?
> >
> > Bill
> >
> > > wrowe 00/07/03 08:24:25
> > >
> > > Modified: . STATUS
> > > src CHANGES
> > > Log:
> > > Bringing these up to date.
> > >
> > > Index: STATUS
> > > ===================================================================
> > > RELEASE SHOWSTOPPERS:
> > >
> > > - * Add a simple Win32 hold console open patch (wait for close or
> > > - the ESC key, with a nice message) if the server died a
> > > - bad death (non-zero exit code) in console mode.
> > > - OtherBill posted
<00...@corecomm.net>
> > > - patch to address this and the NT service log to the list,
and
> > > - is awaiting comments.
> > > -
> > > - * Document the --ntservice flag for Win32 (not a user option,
only for
> > > - launching apache.exe from the WinNT service control
manager).
> > > - OtherBill will do so.
> > > -
> > > * Resolve the status message that the ServerName has been
overridden.
> > > Consensus says this should not appear to the user's
console, but
> > > might be an appropriate information entry to log. The
problem is
> > > that we resolve this before log files are open.
Resolutions?
> > > + Jeff Tarwick is reviewing.
> > >
> > >
> > > Index: CHANGES
> > > ===================================================================
> > > Changes with Apache 1.3.13
> > >
> > > + *) Win32 NT and 2000 services now capture stderr messages that
occur
> > > + before Apache's logs are opened to the Application Event Log.
> > > + Console and Win9x services now hold the console open for 30
seconds
> > > + (and may be dismissed with the <ESC> key) if they exit with an
error.
> > > + [William Rowe]
> > > +
> >
> >
> >
>
>
Re: cvs commit: apache-1.3/src CHANGES
Posted by Bill Stoddard <re...@attglobal.net>.
+1 on releasing next week.
Bill
> I think this wraps it... there are a few testers still bashing.
>
> Would have polled again for votes, but having another handful of
> apbugs duplicate reports in my inbox drove me over the edge :)
> All we need is a "Win32 services were radically overhauled in
> 1.3.13, please download it and try to reproduce your problem" button.
>
> I can't find a place to document --ntservice that won't confuse
> the user. Since there are no suggestions, I've popped it from the
> showstoppers queue. It's similar to the -Z opt, and that is also
> undocumented since it doesn't apply to the user themselves.
>
> If we can reach an agreement on the defaulted ServerName messages
> (remembering the logs aren't opened when we find_fqdn() ) then we
> should be ready to roll.
>
> Arguments pro/con? Anything missing? Anyone want to choose a date?
>
> Bill
>
> > wrowe 00/07/03 08:24:25
> >
> > Modified: . STATUS
> > src CHANGES
> > Log:
> > Bringing these up to date.
> >
> > Index: STATUS
> > ===================================================================
> > RELEASE SHOWSTOPPERS:
> >
> > - * Add a simple Win32 hold console open patch (wait for close or
> > - the ESC key, with a nice message) if the server died a
> > - bad death (non-zero exit code) in console mode.
> > - OtherBill posted <00...@corecomm.net>
> > - patch to address this and the NT service log to the list, and
> > - is awaiting comments.
> > -
> > - * Document the --ntservice flag for Win32 (not a user option, only for
> > - launching apache.exe from the WinNT service control manager).
> > - OtherBill will do so.
> > -
> > * Resolve the status message that the ServerName has been overridden.
> > Consensus says this should not appear to the user's console, but
> > might be an appropriate information entry to log. The problem is
> > that we resolve this before log files are open. Resolutions?
> > + Jeff Tarwick is reviewing.
> >
> >
> > Index: CHANGES
> > ===================================================================
> > Changes with Apache 1.3.13
> >
> > + *) Win32 NT and 2000 services now capture stderr messages that occur
> > + before Apache's logs are opened to the Application Event Log.
> > + Console and Win9x services now hold the console open for 30 seconds
> > + (and may be dismissed with the <ESC> key) if they exit with an error.
> > + [William Rowe]
> > +
>
>
>