Re: Plan for feature freeze?

Hello,<br /><br /> Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If
itdoesn't make<br /> it by August 1st, it doesn't make it.<br /><br /> This could also lead to other things. For
exampleif we have Win32 and PITR calling it 7.5 is a mistake (IMHO) it should<br /> be 8.0 etc...<br /><br />
Sincerely,<br/><br /> Joshua D. Drake<br /><br /><br /> Sincerely,<br /><br /> Joshua D. Drake<br /><br /><br /> Bruce
Momjianwrote: <blockquote cite="mid200404302057.i3UKvnW17466@candle.pha.pa.us" type="cite"><pre wrap="">Marc G.
Fournierwrote: </pre><blockquote type="cite"><pre wrap="">On Fri, 30 Apr 2004, Bruce Momjian wrote:
 
   </pre><blockquote type="cite"><pre wrap="">Marc G. Fournier wrote:     </pre><blockquote type="cite"><blockquote
type="cite"><blockquotetype="cite"><pre wrap="">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 ...           </pre></blockquote><pre wrap="">OK, what is the plan for
featurefreeze?
 

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?         </pre></blockquote><pre wrap="">1 of the major features
thatare 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 ...       </pre></blockquote><pre wrap="">OK,
butI 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.     </pre></blockquote><pre wrap="">No no ... the
dateisn'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 ...   </pre></blockquote><pre wrap="">
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.
 </pre></blockquote><br /><br /><pre class="moz-signature" cols="72">-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - <a class="moz-txt-link-abbreviated" href="mailto:jd@commandprompt.com">jd@commandprompt.com</a> - <a
class="moz-txt-link-freetext"href="http://www.commandprompt.com">http://www.commandprompt.com</a>
 
PostgreSQL Replicator -- production quality replication for PostgreSQL</pre>