Skip site navigation (1) Skip section navigation (2)

Re: pgsql/src/interfaces/odbc/windev README.txt bi ...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/interfaces/odbc/windev README.txt bi ...
Date: 2002-01-11 05:18:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
> > The only but very significant reason I can see about psqlodbc
> > CVS is that people can see (nearly) up to date source at the
> > official place. People can compile it by themselves and try it.
> A fair point.  Other projects than this would likely already have
> a CVS branch going for the-next-version.  Historically we've not
> done that, so as to avoid having to double-patch bug fixes into
> two separate branches.  But this release cycle is going so darn
> slow that I'm half inclined to agree that making a 7.3 branch now
> would be better.
> [ Or, we could get off our collective rears and get 7.2 out the
> door.  Hiroshi is not at fault, but some of us on this side of
> the Pacific are ... ]

The only problem with a 7.3 branch now is double-patching, but I am
willing to do it for my stuff and the stuff I apply.  Our post-final .0
release has very few patches these days so branching is not as big a
deal, _and_ some of us are fulltime so can do the double-patching.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-committers by date

Next:From: momjianDate: 2002-01-11 05:55:01
Subject: pgsql/src/bin/pg_dump pg_upgrade
Previous:From: Tom LaneDate: 2002-01-11 05:02:45
Subject: Re: pgsql/src/interfaces/odbc/windev README.txt bi ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group