|
13 | 13 | <H1>Developer's Frequently Asked Questions (FAQ) for
|
14 | 14 | PostgreSQL</H1>
|
15 | 15 |
|
16 |
| - <P>Last updated: Sat Mar 3 11:12:29 EST 2007</P> |
| 16 | + <P>Last updated: Mon Mar 5 13:03:51 EST 2007</P> |
17 | 17 |
|
18 | 18 | <P>Current maintainer: Bruce Momjian (<A href=
|
19 | 19 | "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
|
@@ -55,9 +55,7 @@ <H2>General Questions</H2>
|
55 | 55 | assistance?<BR>
|
56 | 56 | <A href="#item1.18">1.18</A>) How do I get involved in PostgreSQL web
|
57 | 57 | site development?<BR>
|
58 |
| - <A href="#item1.19">1.19</A>) What is the timeline for the next major |
59 |
| - PostgreSQL release?<BR> |
60 |
| - <A href="#item1.20">1.20</A>) Why haven't you replaced CVS with SVN, Git, |
| 58 | + <A href="#item1.19">1.19</A>) Why haven't you replaced CVS with SVN, Git, |
61 | 59 | Monotone, VSS, <insert your favorite SCM system here>?
|
62 | 60 |
|
63 | 61 |
|
@@ -713,35 +711,23 @@ <H3 id="item1.18">1.18) How do I get involved in PostgreSQL
|
713 | 711 | , the code for the next version of the website is under the
|
714 | 712 | "portal" module.</P>
|
715 | 713 |
|
716 |
| - <H3 id="item1.19">1.19) What is the timeline for the next major |
717 |
| - PostgreSQL release?</H3> |
718 |
| - |
719 |
| - <P>The development schedule for the 8.3 release is:</P> |
720 |
| - <UL> |
721 |
| - <LI>March 1, 2007 - Initial community review of all major feature patches</LI> |
722 |
| - <LI>April 1, 2007 - Feature freeze, all patches must be submitted for review and application</LI> |
723 |
| - <LI>mid-May, 2007 - All patches applied, beta testing begins</LI> |
724 |
| - <LI>July, 2007 - Release of 8.3.0</LI> |
725 |
| - </UL> |
726 |
| - |
727 |
| - <P>Patches that appear after appropriate dates are typically |
728 |
| - not applied but held for the next major release.</P> |
729 |
| - |
730 |
| - <H3 id="item1.20">1.20) Why haven't you replaced CVS with SVN, Git, |
731 |
| - Monotone, VSS, <insert your favorite SCMS here>?</H3> |
732 |
| - |
733 |
| - <P>Currently the core developers see no SCMS that will provide |
734 |
| - enough benefit to outwiegh the pain involved in moving to a new |
735 |
| - SCMS. Typical problems that must be addressed by any new SCMS include:</P> |
736 |
| - <ul> |
737 |
| - <li>Run natively on all of our <a href="http://www.postgresql.org/docs/current/interactive/supported-platforms.html">supported platforms</a>.</li> |
738 |
| - <li>Integrate into the <a href="http://pgbuildfarm.org/">Buildfarm</a>.</li> |
739 |
| - <li>Import our entire CVS Repository while preserving complete history.</li> |
740 |
| - <li>Allow for anonymous checkouts.</li> |
741 |
| - </ul> |
742 |
| - <P>Currently there is no intention for switching to a new SCMS until at least the |
743 |
| - end of the 8.4 development cycle sometime in late 2008. For more information |
744 |
| - please refer to the mailing list archives.</P> |
| 714 | + <H3 id="item1.19">1.19) Why haven't you replaced CVS with SVN, Git, |
| 715 | + Monotone, VSS, <insert your favorite SCMS here>?</H3> |
| 716 | + |
| 717 | + <P>Currently the core developers see no SCMS that will provide |
| 718 | + enough benefit to outwiegh the pain involved in moving to a new |
| 719 | + SCMS. Typical problems that must be addressed by any new SCMS include:</P> |
| 720 | + |
| 721 | + <ul> |
| 722 | + <li>Run natively on all of our <a href="http://www.postgresql.org/docs/current/interactive/supported-platforms.html">supported platforms</a>.</li> |
| 723 | + <li>Integrate into the <a href="http://pgbuildfarm.org/">Buildfarm</a>.</li> |
| 724 | + <li>Import our entire CVS Repository while preserving complete history.</li> |
| 725 | + <li>Allow for anonymous checkouts.</li> |
| 726 | + </ul> |
| 727 | + |
| 728 | + <P>Currently there is no intention for switching to a new SCMS until at least the |
| 729 | + end of the 8.4 development cycle sometime in late 2008. For more information |
| 730 | + please refer to the mailing list archives.</P> |
745 | 731 |
|
746 | 732 |
|
747 | 733 | <H2>Technical Questions</H2>
|
|
0 commit comments