You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stefan Fritsch <sf...@sfritsch.de> on 2011/03/11 23:00:53 UTC

GA

On Tuesday 01 March 2011, Jim Jagielski wrote:
> This is our first Beta release; Based on the feedback and result
> from this Beta, the hope is to push for a GA by the end of
> March (2011)!

FWIW, I would prefer another beta in April and tagging GA at or 
directly after the hackathon at Knockree (mid-May). There are still a 
number of things I want to have in 2.4 but I won't have much time in 
March.

Really nice to have would be:
- change ap_pcfg_* API to allow error handling (working on it)
- change mod_include to (optionally) use the new ap_expr parser
- add document_root to request_rec (there was a patch on the list 
IIRC) for use in mass vhost modules

Less important but still nice to have:
- Fix Solaris LDAP support (PR 42682). This needs no API change but 
the chance of breaking something is so high that I fear the fix would 
never be backported to 2.4.x.

Re: GA

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/17/2011 12:34 PM, William A. Rowe Jr. wrote:
> On 3/17/2011 10:34 AM, Jeff Trawick wrote:
>> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>>> This is our first Beta release; Based on the feedback and result
>>>> from this Beta, the hope is to push for a GA by the end of
>>>> March (2011)!
>>>
>>> FWIW, I would prefer another beta in April and tagging GA at or
>>> directly after the hackathon at Knockree (mid-May). There are still a
>>> number of things I want to have in 2.4 but I won't have much time in
>>> March.
>>
>> That sounds reasonable to me, but then I have my own little project
>> I'd like to finish up in time for the next beta :)
> 
> I'd like to go ahead with a fresh beta image before month end, and am happy
> to RM one.  Whatever is in the tree by the 28th will be in the next beta,
> but I'd still expect a (last?) beta following Knockree.  It's been several
> weeks since the last beta and was never even published on our site.  So lets
> go ahead and freshen it frequently.

(And perhaps another in the later part of April, too?)  That would end up
giving us a fresh beta roughly every 3-4 weeks.

Re: GA

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/17/2011 10:34 AM, Jeff Trawick wrote:
> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>> This is our first Beta release; Based on the feedback and result
>>> from this Beta, the hope is to push for a GA by the end of
>>> March (2011)!
>>
>> FWIW, I would prefer another beta in April and tagging GA at or
>> directly after the hackathon at Knockree (mid-May). There are still a
>> number of things I want to have in 2.4 but I won't have much time in
>> March.
> 
> That sounds reasonable to me, but then I have my own little project
> I'd like to finish up in time for the next beta :)

I'd like to go ahead with a fresh beta image before month end, and am happy
to RM one.  Whatever is in the tree by the 28th will be in the next beta,
but I'd still expect a (last?) beta following Knockree.  It's been several
weeks since the last beta and was never even published on our site.  So lets
go ahead and freshen it frequently.



Re: GA

Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Mar 17, 2011 at 2:31 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> On Mar 17, 2011, at 11:34 AM, Jeff Trawick wrote:
>
>> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>>> This is our first Beta release; Based on the feedback and result
>>>> from this Beta, the hope is to push for a GA by the end of
>>>> March (2011)!
>>>
>>> FWIW, I would prefer another beta in April and tagging GA at or
>>> directly after the hackathon at Knockree (mid-May). There are still a
>>> number of things I want to have in 2.4 but I won't have much time in
>>> March.
>>
>> That sounds reasonable to me, but then I have my own little project
>> I'd like to finish up in time for the next beta :)
>>
>
> My plan is to have another beta the end of March, another
> in April and GA in May (at the latest)...
>
> Sound reasonable?

+1

Re: GA

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/17/2011 3:40 PM, William A. Rowe Jr. wrote:
> On 3/17/2011 1:31 PM, Jim Jagielski wrote:
>>
>> My plan is to have another beta the end of March, another
>> in April and GA in May (at the latest)...
> 
> Well, if we presume that people will invent and collaborate to refine
> some "cool stuff" at Wicklow, it isn't unreasonable to guess that such
> a tarball would still be beta and need several weeks of a "large group"
> of final testers and some bug fixes to be realistically be "the best
> available version" and more robust than 2.2.17 in June.  I will vote
> against declaring 'ga' any taraball which can't meet that self-described
> label that we've  assign to every general release for over a dozen years :)

Which was to say, if there are no changes in May that could reasonably be
expected to cause a regression, then the May candidate might be suited
to be GA, but might be better described as /final beta/.  We would have
the best sense of this during the Wicklow hackathon/weekend.


Re: GA

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/18/2011 3:01 PM, Jim Jagielski wrote:
> 
> My hopes are that if people are really wanting to invent and collaborate
> on cool stuff, that they don't wait until a f2f event that the vast
> majority of current httpd developers will not be attending and
> will instead try to start stuff now-ish in hopes of getting a
> GA out sooner rather than changing things so much that any
> momentum achieved up to now is wasted by the addition of lots
> of cool stuff that requires substantial vetting and thus causing
> yet more delays on a release that has already been long enough
> already thank you.

And of course, there is an argument that if the 'final' improvements
are picked up by a late April beta, whomever makes it to wicklow can
start looking at what should be in httpd 3.0, even as 2.4 is introduced
to the world :)

Re: GA

Posted by Jim Jagielski <ji...@jaguNET.com>.
On Mar 19, 2011, at 6:50 AM, Dan Poirier wrote:

> On Fri. 2011-03-18 at 09:03 PM EDT, Nick Kew <ni...@webthing.com> wrote:
> 
>> On 19 Mar 2011, at 00:02, Dan Poirier wrote:
>> 
>>> At some point, do we declare a feature-freeze for what will be 2.4.0?
>> 
>> Features can be added during a release.
> 
> I was just thinking of a temporary pause, that might be helpful in
> getting to a point where trunk is stable enough to feel comfortable
> declaring it 2.4.0.  
> 
> Maybe we don't need anything that formal.  I get the sense that a few
> people have things they'd like to get in before "2.4.0" for some reason,
> but we hardly have a continuous stream of new features being added.
> 

I think as we get closer to GA, most people will be more circumspect
about changing the API willy-nilly... if it needs to be done, then
it should be. 2.4 will be out there, as previous history clearly
shows, for quite a Long Time, and we should ensure the API is
what we need it to be.


Re: GA

Posted by Dan Poirier <po...@pobox.com>.
On Fri. 2011-03-18 at 09:03 PM EDT, Nick Kew <ni...@webthing.com> wrote:

> On 19 Mar 2011, at 00:02, Dan Poirier wrote:
>
>> At some point, do we declare a feature-freeze for what will be 2.4.0?
>
> Features can be added during a release.

I was just thinking of a temporary pause, that might be helpful in
getting to a point where trunk is stable enough to feel comfortable
declaring it 2.4.0.  

Maybe we don't need anything that formal.  I get the sense that a few
people have things they'd like to get in before "2.4.0" for some reason,
but we hardly have a continuous stream of new features being added.

Dan


Re: GA

Posted by Nick Kew <ni...@webthing.com>.
On 19 Mar 2011, at 00:02, Dan Poirier wrote:

> At some point, do we declare a feature-freeze for what will be 2.4.0?

Features can be added during a release.

We will of course need an MMN-major freeze, which is the branch's
promise of API/ABI back-compatibility.  But we can still also add
to the API provided we don't break anything.

-- 
Nick Kew

Re: GA

Posted by Dan Poirier <po...@pobox.com>.
On Fri. 2011-03-18 at 04:01 PM EDT, Jim Jagielski <ji...@jaguNET.com> wrote:

> My hopes are that if people are really wanting to invent and collaborate
> on cool stuff, that they don't wait until a f2f event that the vast
> majority of current httpd developers will not be attending and
> will instead try to start stuff now-ish in hopes of getting a
> GA out sooner rather than changing things so much that any
> momentum achieved up to now is wasted by the addition of lots
> of cool stuff that requires substantial vetting and thus causing
> yet more delays on a release that has already been long enough
> already thank you.

At some point, do we declare a feature-freeze for what will be 2.4.0?

Re: GA

Posted by Jim Jagielski <ji...@jaguNET.com>.
On Mar 17, 2011, at 4:40 PM, William A. Rowe Jr. wrote:

> On 3/17/2011 1:31 PM, Jim Jagielski wrote:
>> 
>> On Mar 17, 2011, at 11:34 AM, Jeff Trawick wrote:
>> 
>>> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>>>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>>>> This is our first Beta release; Based on the feedback and result
>>>>> from this Beta, the hope is to push for a GA by the end of
>>>>> March (2011)!
>>>> 
>>>> FWIW, I would prefer another beta in April and tagging GA at or
>>>> directly after the hackathon at Knockree (mid-May). There are still a
>>>> number of things I want to have in 2.4 but I won't have much time in
>>>> March.
>>> 
>>> That sounds reasonable to me, but then I have my own little project
>>> I'd like to finish up in time for the next beta :)
>>> 
>> 
>> My plan is to have another beta the end of March, another
>> in April and GA in May (at the latest)...
> 
> Well, if we presume that people will invent and collaborate to refine
> some "cool stuff" at Wicklow, it isn't unreasonable to guess that such
> a tarball would still be beta and need several weeks of a "large group"
> of final testers and some bug fixes to be realistically be "the best
> available version" and more robust than 2.2.17 in June.  I will vote
> against declaring 'ga' any taraball which can't meet that self-described
> label that we've  assign to every general release for over a dozen years :)
> 

My hopes are that if people are really wanting to invent and collaborate
on cool stuff, that they don't wait until a f2f event that the vast
majority of current httpd developers will not be attending and
will instead try to start stuff now-ish in hopes of getting a
GA out sooner rather than changing things so much that any
momentum achieved up to now is wasted by the addition of lots
of cool stuff that requires substantial vetting and thus causing
yet more delays on a release that has already been long enough
already thank you.

*grin*

Re: GA

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 3/17/2011 1:31 PM, Jim Jagielski wrote:
> 
> On Mar 17, 2011, at 11:34 AM, Jeff Trawick wrote:
> 
>> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>>> This is our first Beta release; Based on the feedback and result
>>>> from this Beta, the hope is to push for a GA by the end of
>>>> March (2011)!
>>>
>>> FWIW, I would prefer another beta in April and tagging GA at or
>>> directly after the hackathon at Knockree (mid-May). There are still a
>>> number of things I want to have in 2.4 but I won't have much time in
>>> March.
>>
>> That sounds reasonable to me, but then I have my own little project
>> I'd like to finish up in time for the next beta :)
>>
> 
> My plan is to have another beta the end of March, another
> in April and GA in May (at the latest)...

Well, if we presume that people will invent and collaborate to refine
some "cool stuff" at Wicklow, it isn't unreasonable to guess that such
a tarball would still be beta and need several weeks of a "large group"
of final testers and some bug fixes to be realistically be "the best
available version" and more robust than 2.2.17 in June.  I will vote
against declaring 'ga' any taraball which can't meet that self-described
label that we've  assign to every general release for over a dozen years :)

Re: GA

Posted by Jim Jagielski <ji...@jaguNET.com>.
On Mar 17, 2011, at 11:34 AM, Jeff Trawick wrote:

> On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
>> On Tuesday 01 March 2011, Jim Jagielski wrote:
>>> This is our first Beta release; Based on the feedback and result
>>> from this Beta, the hope is to push for a GA by the end of
>>> March (2011)!
>> 
>> FWIW, I would prefer another beta in April and tagging GA at or
>> directly after the hackathon at Knockree (mid-May). There are still a
>> number of things I want to have in 2.4 but I won't have much time in
>> March.
> 
> That sounds reasonable to me, but then I have my own little project
> I'd like to finish up in time for the next beta :)
> 

My plan is to have another beta the end of March, another
in April and GA in May (at the latest)...

Sound reasonable?

Re: GA

Posted by Jeff Trawick <tr...@gmail.com>.
On Fri, Mar 11, 2011 at 5:00 PM, Stefan Fritsch <sf...@sfritsch.de> wrote:
> On Tuesday 01 March 2011, Jim Jagielski wrote:
>> This is our first Beta release; Based on the feedback and result
>> from this Beta, the hope is to push for a GA by the end of
>> March (2011)!
>
> FWIW, I would prefer another beta in April and tagging GA at or
> directly after the hackathon at Knockree (mid-May). There are still a
> number of things I want to have in 2.4 but I won't have much time in
> March.

That sounds reasonable to me, but then I have my own little project
I'd like to finish up in time for the next beta :)