X-Original-To: pgsql-interfaces@postgresql.org Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 65A35476386 for ; Fri, 14 Mar 2003 15:25:51 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h2EKPE421255; Fri, 14 Mar 2003 15:25:14 -0500 (EST) From: Bruce Momjian Message-Id: <200303142025.h2EKPE421255@candle.pha.pa.us> Subject: Re: Prepare and prepare ? In-Reply-To: To: Rudy Lippan Date: Fri, 14 Mar 2003 15:25:14 -0500 (EST) Cc: Dominic Mitchell , pgsql-interfaces@postgresql.org, David Wheeler , dbi-dev@perl.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200303/75 X-Sequence-Number: 3824 To answer your question from a month ago :-), we should have CVS tagged the 1.21 release, but we forgot. I didn't think we were big enough to tag things. :-) We don't have any master plan on development --- we just discuss items and apply patches. --------------------------------------------------------------------------- Rudy Lippan wrote: > On Thu, 13 Feb 2003, Dominic Mitchell wrote: > > > Well at the moment, backwards compatibility is limited to one system at > > our place that needed the funtionality right now. We'll change it to > > use whatever DBD::Pg comes with, however. > > Right, but once it goes into a public release (eg. DBD::Pg 1.22) then you > are stuck supporting it/making a migration path. > > > > With 2, the patch goes in as is and backwards compatibility does not > > > get broken in the next version. Just a thought. > > > > #2 sounds good to me. > > > > The we go this route. > > > The flag was called, "pg_do_utf8", but "pg_enable_utf8" might be a > > better name. > > > > Agreed. pg_enable_utf8 the flag is, then. I'll go apply the patch -- > changing pg_do_utf8 to pg_enable_utf8. > > > > David/Bruce, > > 1. Looking over CVS I don't see a release tag for 1.21. It would proably > be better for whoever did the export of 1.21 to tag up, but if you want I > will set up a release tag for 1.21? > > 2. What is the procedure for adding patches, closing bugs, working with > tasks, and working with feature requests on GBorg... Is there a place > where I can get an overview of how things are done? > > > -r > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073