Hello,
Possible scenario for maintaining 7.3:
Only one or two committers using a two stage cvs... one stage for
testing (not including sandbox), one stage for commit. Scheduled releases based on non-critical fixes. Quarterly? Of
course
critical fixes should be released as soon as plausible.
Separate mailing list for 7.3 issues, concerns etc... Which would help
develop it's own temporary community.
Thoughts?
Joshua D. Drake
Tom Lane wrote:
>Robert Treat <xzilla@users.sourceforge.net> writes:
>
>
>>and the question as i thought was being discussed (or should be
>>discussed) was what is the level of interest in having this work kept in
>>the community cvs tree vs. someone else's quasi-forked branch...
>>
>>
>
>I see no reason that the maintenance shouldn't be done in the community
>CVS archive. The problem is where to find the people who want to do it.
>Of course we have to trust those people enough to give them write access
>to the community archive, but if they can't be trusted with that, one
>wonders who's going to trust their work product either.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
