From 37fc8a667e8a21f6e1942deaf51a6ea8fe484792 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 5 Mar 2007 18:04:03 +0000 Subject: [PATCH] Remove timeline for 8.3 release, now on web site. --- doc/FAQ_DEV | 20 +++------------- doc/src/FAQ/FAQ_DEV.html | 52 +++++++++++++++------------------------- 2 files changed, 22 insertions(+), 50 deletions(-) diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index 31284a8f43..1a43bfa6b6 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -1,7 +1,7 @@ Developer's Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Sat Mar 3 11:12:29 EST 2007 + Last updated: Mon Mar 5 13:03:51 EST 2007 Current maintainer: Bruce Momjian (bruce@momjian.us) @@ -30,8 +30,7 @@ General Questions 1.16) Where can I get a copy of the SQL standards? 1.17) Where can I get technical assistance? 1.18) How do I get involved in PostgreSQL web site development? - 1.19) What is the timeline for the next major PostgreSQL release? - 1.20) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, + 1.19) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, ? Technical Questions @@ -571,20 +570,7 @@ General Questions http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code for the next version of the website is under the "portal" module. - 1.19) What is the timeline for the next major PostgreSQL release? - - The development schedule for the 8.3 release is: - * March 1, 2007 - Initial community review of all major feature - patches - * April 1, 2007 - Feature freeze, all patches must be submitted for - review and application - * mid-May, 2007 - All patches applied, beta testing begins - * July, 2007 - Release of 8.3.0 - - Patches that appear after appropriate dates are typically not applied - but held for the next major release. - - 1.20) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, ? Currently the core developers see no SCMS that will provide enough diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index eb4ad5b7af..4e0af3b20e 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -13,7 +13,7 @@

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Sat Mar 3 11:12:29 EST 2007

+

Last updated: Mon Mar 5 13:03:51 EST 2007

Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -55,9 +55,7 @@ assistance?
1.18) How do I get involved in PostgreSQL web site development?
- 1.19) What is the timeline for the next major - PostgreSQL release?
- 1.20) Why haven't you replaced CVS with SVN, Git, + 1.19) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, <insert your favorite SCM system here>? @@ -713,35 +711,23 @@ , the code for the next version of the website is under the "portal" module.

-

1.19) What is the timeline for the next major - PostgreSQL release?

- -

The development schedule for the 8.3 release is:

-
    -
  • March 1, 2007 - Initial community review of all major feature patches
    • -
  • April 1, 2007 - Feature freeze, all patches must be submitted for review and application
    • -
  • mid-May, 2007 - All patches applied, beta testing begins
    • -
  • July, 2007 - Release of 8.3.0
    • -
- -

Patches that appear after appropriate dates are typically - not applied but held for the next major release.

- -

1.20) Why haven't you replaced CVS with SVN, Git, - Monotone, VSS, <insert your favorite SCMS here>?

- -

Currently the core developers see no SCMS that will provide - enough benefit to outwiegh the pain involved in moving to a new - SCMS. Typical problems that must be addressed by any new SCMS include:

-
    -
  • Run natively on all of our supported platforms.
    • -
  • Integrate into the Buildfarm.
    • -
  • Import our entire CVS Repository while preserving complete history.
    • -
  • Allow for anonymous checkouts.
    • -
-

Currently there is no intention for switching to a new SCMS until at least the - end of the 8.4 development cycle sometime in late 2008. For more information - please refer to the mailing list archives.

+

1.19) Why haven't you replaced CVS with SVN, Git, + Monotone, VSS, <insert your favorite SCMS here>?

+ +

Currently the core developers see no SCMS that will provide + enough benefit to outwiegh the pain involved in moving to a new + SCMS. Typical problems that must be addressed by any new SCMS include:

+ +
    +
  • Run natively on all of our supported platforms.
    • +
  • Integrate into the Buildfarm.
    • +
  • Import our entire CVS Repository while preserving complete history.
    • +
  • Allow for anonymous checkouts.
    • +
+ +

Currently there is no intention for switching to a new SCMS until at least the + end of the 8.4 development cycle sometime in late 2008. For more information + please refer to the mailing list archives.

Technical Questions

-- 2.40.0