Re: Plan for feature freeze?

<br /><blockquote cite="mid20040430202625.Q45839@ganymede.hub.org" type="cite"><blockquote type="cite"><pre wrap="">
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.   </pre></blockquote><pre wrap="">
We could go for September 1st, which would mean most are back from
holidays, in order to do beta testing ... and no, I'm not serious ...
 </pre></blockquote> Why not? Seemed like a fairly good argument both yours and mine ;)<br /><br /> Sincerely,<br /><br
/>Joshua D. Drake<br /><br /><br /><br /><blockquote cite="mid20040430202625.Q45839@ganymede.hub.org" type="cite"><pre
wrap="">
----
Marc G. Fournier           Hub.Org Networking Services (<a class="moz-txt-link-freetext"
href="http://www.hub.org">http://www.hub.org</a>)
Email: <a class="moz-txt-link-abbreviated" href="mailto:scrappy@hub.org">scrappy@hub.org</a>           Yahoo!: yscrappy
            ICQ: 7615664 </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>