Skip site navigation (1) Skip section navigation (2)

Re: Plan for feature freeze?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Plan for feature freeze?
Date: 2004-04-30 23:17:59
Message-ID: 4092DEA7.2040201@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hello,

Why don't we just set a freeze of August 1st? Give everyone just a 
little extra time. No float. If it doesn't make
it by August 1st, it doesn't make it.

This could also lead to other things. For example if we have Win32 and 
PITR calling it 7.5 is a mistake (IMHO) it should
be 8.0 etc...

Sincerely,

Joshua D. Drake


Sincerely,

Joshua D. Drake


Bruce Momjian wrote:

>Marc G. Fournier wrote:
>  
>
>>On Fri, 30 Apr 2004, Bruce Momjian wrote:
>>
>>    
>>
>>>Marc G. Fournier wrote:
>>>      
>>>
>>>>>>No, I agree that that would be foolish ... but there has also been alot
>>>>>>done on the code over the past few months that even *one* of those
>>>>>>features should be enough to put it over the top ...
>>>>>>            
>>>>>>
>>>>>OK, what is the plan for feature freeze?
>>>>>
>>>>>As we going for June 1, and making no adjustments?  If we have no major
>>>>>features done, we still do June 1.  Or are we waiting for one or several
>>>>>major features to complete and then set a freeze date?
>>>>>          
>>>>>
>>>>1 of the major features that are currently on tap (ie. Win32) *or* June
>>>>1st, whichever happens to be the longer of the two ...
>>>>
>>>>Indications that I've seen through this discussion are that Win32 can, and
>>>>should, be done by June 1st ...so extending may be a moot point anyway ...
>>>>        
>>>>
>>>OK, but I am worried about giving Win32 special treatment, and having
>>>the date float like that until Win32 is done.  This is what we did with
>>>the SMP fixed in 7.3 and the date slipped week by week.  We have to set
>>>the date firm early on.  I think we all agreed to that in the past.
>>>      
>>>
>>No no ... the date isn't floating on Win32 ... the date is floating on one
>>of the major features (PITR, 2PC, etc) ... if Win32 happens to be the
>>first major feature, so be it, but it is not contigent on Win32 ...
>>    
>>
>
>So you are floating the entire thing.  I am tired of discussing this. 
>You call the freeze and when it is a disaster, you can take the credit.
>
>I am not worrying about any freeze date anymore.  You freeze whenever
>you want to.
>
>Floating a freeze data has always been a failure.  Let's watch it happen
>again.
>
>  
>


-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL

In response to

Responses

pgsql-hackers by date

Next:From: Marc G. FournierDate: 2004-04-30 23:27:19
Subject: Re: Plan for feature freeze?
Previous:From: Andrew DunstanDate: 2004-04-30 23:13:34
Subject: Re: Plan for feature freeze?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group