public inbox for [email protected]  
help / color / mirror / Atom feed
From: Joshua D. Drake <[email protected]>
To: PostgreSQL WWW <[email protected]>
Subject: Second try for roadmap.html
Date: Tue, 27 Feb 2007 11:08:12 -0800
Message-ID: <[email protected]> (raw)


-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


Index: roadmap.html
===================================================================
RCS file: /usr/local/cvsroot/pgweb/portal/template/en/developer/roadmap.html,v
retrieving revision 1.8
diff -c -r1.8 roadmap.html
*** roadmap.html	19 Oct 2006 01:32:36 -0000	1.8
--- roadmap.html	27 Feb 2007 19:05:28 -0000
***************
*** 5,19 ****
  <h1>Roadmap</h1>
  
  <p>PostgreSQL is a non-commercial, all volunteer, free software project, and as such there is no formal list of 
! feature requirements required for development. We really do follow the mantra of letting developers scratch their own itches.</p>
  
- <p>That said, there is an informal list of items that have been agreed upon by the PostgreSQL developers as things that need to 
- worked upon, known as the <a href="/docs/faqs.TODO.html">TODO</a> list. Items on the list can be marked as
- completed in development, "claimed" by a developer and being activly worked on, or unmarked meaning that the item is likely not 
- being activly worked on. </p>
- 
- <p>There are also two lists for "unapplied patches" that have been submitted for inclusion into PostgreSQL,
- one for the <a href="http://momjian.postgresql.org/cgi-bin/pgpatches">patches saved for the current release</a> and one for 
- <a href="http://momjian.postgresql.org/cgi-bin/pgpatches_hold">patches saved for the next release</a>. Once a patch has been submitted 
- and saved in the queue, it is a good bet that the particular feature will make it into the appropriate release.</p> 
  
--- 5,23 ----
  <h1>Roadmap</h1>
  
  <p>PostgreSQL is a non-commercial, all volunteer, free software project, and as such there is no formal list of 
! feature requirements required for development. However, we do try to adhere to a reasonable release schedule.</p>
! 
! <h2>Release Schedule</h2>
! <ul>
!   <li>March 31, 2007 - Feature Freeze</li>
!   <li>May-June 2007 - Beta begins</li>
!   <li>July-August 2007 - 8.3 Released</li>
!   <li>September 2007 - 8.4 development begins</li>
!   <li>March 31, 2008  Feature freeze for 8.4 (tentative)</li>
! </ul>
! 
! 
! 
! 
  
  


Attachments:

  [text/plain] roadmap.diff (2.0K, 2-roadmap.diff)
  download | inline diff:
Index: roadmap.html
===================================================================
RCS file: /usr/local/cvsroot/pgweb/portal/template/en/developer/roadmap.html,v
retrieving revision 1.8
diff -c -r1.8 roadmap.html
*** roadmap.html	19 Oct 2006 01:32:36 -0000	1.8
--- roadmap.html	27 Feb 2007 19:05:28 -0000
***************
*** 5,19 ****
  <h1>Roadmap</h1>
  
  <p>PostgreSQL is a non-commercial, all volunteer, free software project, and as such there is no formal list of 
! feature requirements required for development. We really do follow the mantra of letting developers scratch their own itches.</p>
  
- <p>That said, there is an informal list of items that have been agreed upon by the PostgreSQL developers as things that need to 
- worked upon, known as the <a href="/docs/faqs.TODO.html">TODO</a> list. Items on the list can be marked as
- completed in development, "claimed" by a developer and being activly worked on, or unmarked meaning that the item is likely not 
- being activly worked on. </p>
- 
- <p>There are also two lists for "unapplied patches" that have been submitted for inclusion into PostgreSQL,
- one for the <a href="http://momjian.postgresql.org/cgi-bin/pgpatches">patches saved for the current release</a> and one for 
- <a href="http://momjian.postgresql.org/cgi-bin/pgpatches_hold">patches saved for the next release</a>. Once a patch has been submitted 
- and saved in the queue, it is a good bet that the particular feature will make it into the appropriate release.</p> 
  
--- 5,23 ----
  <h1>Roadmap</h1>
  
  <p>PostgreSQL is a non-commercial, all volunteer, free software project, and as such there is no formal list of 
! feature requirements required for development. However, we do try to adhere to a reasonable release schedule.</p>
! 
! <h2>Release Schedule</h2>
! <ul>
!   <li>March 31, 2007 - Feature Freeze</li>
!   <li>May-June 2007 - Beta begins</li>
!   <li>July-August 2007 - 8.3 Released</li>
!   <li>September 2007 - 8.4 development begins</li>
!   <li>March 31, 2008  Feature freeze for 8.4 (tentative)</li>
! </ul>
! 
! 
! 
! 
  
  


view thread (18+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: Second try for roadmap.html
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox