You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Behlendorf <br...@hyperreal.org> on 1998/05/29 09:41:48 UTC
1.3b8 ==> 1.3.0
Proposal: the next release is 1.3.0, not 1.3b8.
Rational:
a) the fallout from the significant child_spawn changes have been settled
b) STATUS is looking fairly clean, all things considered. Still have a
Win95 showstopper, but if no one wants to deal with it...
c) bug reports are starting to decline in seriousness.
d) We have this morbid fear of x.y.1 releases we need to get over. Fact
is there are people who won't use .0 of any product, but will wait for .1,
.2, maybe even .3 or .4. Remember Apache 1.2.0?
e) everyone and their dog wants to move on to 2.0.
Timeline:
There are a few more patches to integrate, a few cleanups and audits that
should be done. As RM I should have realized I was going to be out of town
Sunday through Wednesday, so a June 1st release would not work. June 5th?
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction brian@apache.org
brian@hyperreal.org
Re: 1.3b8 ==> 1.3.0
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Brian Behlendorf wrote:
>
> Proposal: the next release is 1.3.0, not 1.3b8.
>
> Rational:
Sounds like it. It even sounds like a rationale. :-D
> d) We have this morbid fear of x.y.1 releases we need to get over.
> Fact is there are people who won't use .0 of any product, but
> will wait for .1, .2, maybe even .3 or .4. Remember Apache
> 1.2.0?
I agree that this is something we should try to get over.
However.. once 1.3.0 is out does that necessarily imply no
more features in 1.3.x? I personally don't like that. Sure,
most energy should go toward 2.0 - but I'd still appreciate
the possibility of feature cycles for 1.3.x follow-ons.
#ken P-)}
Ken Coar <http://Web.Golux.Com/coar/>
Apache Group member <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>
Re: 1.3b8 ==> 1.3.0
Posted by Brian Behlendorf <br...@hyperreal.org>.
At 07:57 AM 5/29/98 -0400, Jim Jagielski wrote:
>> There are a few more patches to integrate, a few cleanups and audits that
>> should be done. As RM I should have realized I was going to be out of town
>> Sunday through Wednesday, so a June 1st release would not work. June 5th?
>
>Sounds good as well. If you like, I can roll the release the 1st or so,
>then we can test it between then and the 5th and formally release
>then.
This sounds good to me. It'd be good to post it and then announce it 24
hours later so that mirror sites have a chance of having the release when
we make the announcement, as well as give us a chance to build binary
releases too.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction brian@apache.org
brian@hyperreal.org
Re: 1.3b8 ==> 1.3.0
Posted by Randy Terbush <ra...@Covalent.NET>.
+1
Most outstanding issues have been resolved on my end. I would like to
get the change for md5.h that I just mentioned, but that is minor.
Brian Behlendorf <br...@hyperreal.org> writes:
> Proposal: the next release is 1.3.0, not 1.3b8.
>
> Rational:
>
> a) the fallout from the significant child_spawn changes have been settled
> b) STATUS is looking fairly clean, all things considered. Still have a
> Win95 showstopper, but if no one wants to deal with it...
> c) bug reports are starting to decline in seriousness.
> d) We have this morbid fear of x.y.1 releases we need to get over. Fact
> is there are people who won't use .0 of any product, but will wait for .1,
> .2, maybe even .3 or .4. Remember Apache 1.2.0?
> e) everyone and their dog wants to move on to 2.0.
>
> Timeline:
>
> There are a few more patches to integrate, a few cleanups and audits that
> should be done. As RM I should have realized I was going to be out of town
> Sunday through Wednesday, so a June 1st release would not work. June 5th?
>
> Brian
>
>
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> pure chewing satisfaction brian@apache.org
> brian@hyperreal.org
Re: 1.3b8 ==> 1.3.0
Posted by Brian Behlendorf <br...@hyperreal.org>.
At 10:53 PM 6/1/98 +0200, Martin Kraemer wrote:
>And I have more proxy fixes to come.
Since you're paying attention to the proxy code these days, could you take
a look at PR2277, a patch to fix a bug in aborted xfers being cached, as
well as complete caching of those aborted xfers? The author is thinking
about adding a few things to it, along the lines of what Squid does.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction brian@apache.org
brian@hyperreal.org
Re: 1.3b8 ==> 1.3.0
Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Mon, Jun 01, 1998 at 01:52:44PM -0700, Dean Gaudet wrote:
>
> No I'm still +1 -- I had one comment on your patch (the missing
> ap_cleanup_for_exec). The above comment was because I thought you guys
> were talking about some other new concept.
Yes, I incorporated that (replaced by comment with the ap_cleanup_for_exec()
call) without sending out a second [PATCH]. But as nobody seems to have
tested it, and only you and Randy studied the code, I agree with Jim
that it's best to add this to the 1.3.1-to-be.
And I have more proxy fixes to come. That will mostly be code cleanup,
improved ftp authentication (by Basic authentication method instead of
clean text URL password). I'm currently testing and will post some
questions to the list soon.
I'm also thinking about a last-modified header for ftp-proxy served files.
That requires an intermediate LIST request and an "ls -l" unparser, which
I'll have to write (it's in wget, but wget is GPL'ed). There's also the
problem with time zones... Are ftp directory listimgs local or GMTime?
Martin
--
| S I E M E N S | <Ma...@mch.sni.de> | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
Re: 1.3b8 ==> 1.3.0
Posted by Dean Gaudet <dg...@arctic.org>.
On Mon, 1 Jun 1998, Martin Kraemer wrote:
> On Fri, May 29, 1998 at 08:13:17PM -0700, Dean Gaudet wrote:
> > Hey by background gc do you mean an external program that goes around
> > doing it, rather than something that happens to get spawned as a
> > side-effect of a request? yeah would be cool.
>
> No, sorry. We talked about my patch (based on a discussion between you
> and dirk last fall) where the GC is spawned off by a double-fork()
> and setsid()/setpgrp() to avoid blocking the current request to finish.
>
> > I'm +1 on the fixes going in as well.
>
> Hmm... Under these circumstances, does that mean +0?
No I'm still +1 -- I had one comment on your patch (the missing
ap_cleanup_for_exec). The above comment was because I thought you guys
were talking about some other new concept.
Dean
Re: 1.3b8 ==> 1.3.0
Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Fri, May 29, 1998 at 08:13:17PM -0700, Dean Gaudet wrote:
> Hey by background gc do you mean an external program that goes around
> doing it, rather than something that happens to get spawned as a
> side-effect of a request? yeah would be cool.
No, sorry. We talked about my patch (based on a discussion between you
and dirk last fall) where the GC is spawned off by a double-fork()
and setsid()/setpgrp() to avoid blocking the current request to finish.
> I'm +1 on the fixes going in as well.
Hmm... Under these circumstances, does that mean +0?
Too late anyway, no?
Martin
--
| S I E M E N S | <Ma...@mch.sni.de> | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
Re: 1.3b8 ==> 1.3.0
Posted by Dean Gaudet <dg...@arctic.org>.
Hey by background gc do you mean an external program that goes around
doing it, rather than something that happens to get spawned as a
side-effect of a request? yeah would be cool.
I'm +1 on the fixes going in as well.
Dean
On 29 May 1998, Randy Terbush wrote:
> Martin Kraemer <Ma...@mch.sni.de> writes:
> > On Fri, May 29, 1998 at 01:06:43AM -0700, Dean Gaudet wrote:
> > > +1
> > >
> > > Dean
> >
> > Oops - forgot to say: +1 for me too.
> > The proxy fixups will go into 1.3.1 then. Okay? Or who's in favor of a
> > backgrounded proxy GC?
>
> Backgrounding the GC would be very cool.
>
> As for holding proxy changes for 1.3.1.... The proxy code has always
> gotten special treatment when it comes to commits since it seems to
> lag behind the rest of the server development. I would support getting
> it in there now if the changes are ready and tested.
>
>
>
Re: 1.3b8 ==> 1.3.0
Posted by Randy Terbush <ra...@Covalent.NET>.
Martin Kraemer <Ma...@mch.sni.de> writes:
> On Fri, May 29, 1998 at 01:06:43AM -0700, Dean Gaudet wrote:
> > +1
> >
> > Dean
>
> Oops - forgot to say: +1 for me too.
> The proxy fixups will go into 1.3.1 then. Okay? Or who's in favor of a
> backgrounded proxy GC?
Backgrounding the GC would be very cool.
As for holding proxy changes for 1.3.1.... The proxy code has always
gotten special treatment when it comes to commits since it seems to
lag behind the rest of the server development. I would support getting
it in there now if the changes are ready and tested.
Re: 1.3b8 ==> 1.3.0
Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Fri, May 29, 1998 at 01:06:43AM -0700, Dean Gaudet wrote:
> +1
>
> Dean
Oops - forgot to say: +1 for me too.
The proxy fixups will go into 1.3.1 then. Okay? Or who's in favor of a
backgrounded proxy GC?
Martin
--
| S I E M E N S | <Ma...@mch.sni.de> | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
Re: 1.3b8 ==> 1.3.0
Posted by Dean Gaudet <dg...@arctic.org>.
+1
Dean
On Fri, 29 May 1998, Brian Behlendorf wrote:
>
> Proposal: the next release is 1.3.0, not 1.3b8.
>
> Rational:
>
> a) the fallout from the significant child_spawn changes have been settled
> b) STATUS is looking fairly clean, all things considered. Still have a
> Win95 showstopper, but if no one wants to deal with it...
> c) bug reports are starting to decline in seriousness.
> d) We have this morbid fear of x.y.1 releases we need to get over. Fact
> is there are people who won't use .0 of any product, but will wait for .1,
> .2, maybe even .3 or .4. Remember Apache 1.2.0?
> e) everyone and their dog wants to move on to 2.0.
>
> Timeline:
>
> There are a few more patches to integrate, a few cleanups and audits that
> should be done. As RM I should have realized I was going to be out of town
> Sunday through Wednesday, so a June 1st release would not work. June 5th?
>
> Brian
>
>
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> pure chewing satisfaction brian@apache.org
> brian@hyperreal.org
>