. Reedstrom; Nigel
J. Andrews; Marc G. Fournier; Constantin Teodorescu; Cmaj; Boyan
Filipov; Boyan Dzambazov; Bartus. L; Brett Schwarz
Subject: Re: [HACKERS] internal voting
...
> If nobody feels like managing this - let's give it a little bit of life
and
> move it a bit forwards - and then
Ross J. Reedstrom writes:
> All very practical, execpt for one point: the people being pulled togther
> for this _have_ code, with nowhere to put it: they've been developing
> new features for pgaccess, on top of the stable pgsql. Tracking CVS
> tip means that the current version of pgaccess ther
On 2002.05.11 14:15 Peter Eisentraut wrote:
> Ross J. Reedstrom writes:
>
> > All very practical, execpt for one point: the people being pulled
> togther
> > for this _have_ code, with nowhere to put it: they've been
> developing
> > new features for pgaccess, on top of the stable pgsql. Tracking
...
> If nobody feels like managing this - let's give it a little bit of life and
> move it a bit forwards - and then talk again.
Iavor, I meant to be helpful; I was trying to put a name on The New
Group of Enthusiastic Developers Who Are Interested In Advancing
Pgaccess and shortened it to "Iavo
> Actually, CVS can support this just fine (I'll mention how below) but
> afaict the discussion is moot because Iavor has declared that his group
> prefers to take another path for now.
>
>- Thomas
It is not 'my' group! I just happened to ask somebody in my company to patch
so
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> We went through a very similar situation with the JDBC driver a release
> ago. A number of people had developed fixes or features for the driver
> and no one was collecting them. We've got those people working on the 7.2
> branch and everything work
On Sat, 11 May 2002, Tom Lane wrote:
> Au contraire --- what the JDBC folk did (and still are doing) was to
> make "unofficial" releases consisting of snapshots pulled from their
> chunk of the CVS tree. There were people making use of the "7.2 branch"
> of JDBC long before the 7.2 server went b
...
> While it would be nice to have one pgaccess that can work with any pgsql
> backend, that's not currently the case. One solution would be to work
> on the release branch, but that's discouraged - bug fixes only.
Actually, CVS can support this just fine (I'll mention how below) but
afaict the
On Fri, May 10, 2002 at 11:24:40PM +0200, Peter Eisentraut wrote:
> Iavor Raytchev writes:
>
> > 3] Still - the only thing that is not clear to me is - who is going to
> > collect all patches and make one whole form them. As long as each of us
> > works on a different thing - this should not be a
Iavor Raytchev writes:
> 3] Still - the only thing that is not clear to me is - who is going to
> collect all patches and make one whole form them. As long as each of us
> works on a different thing - this should not be a big problem, but still -
> needs to be one person.
As far as I'm concerned
[Note, I've changed the headers so everyone on the original distribution list
is getting a copy via Bcc, including -hackers. It was the simplest way I could
think of making certain the discussion moved to -interfaces as Marc requested.]
On Sat, 11 May 2002, Bartus Levente wrote:
> ... I think,
On Fri, 10 May 2002 10:58:28 +0200
"Iavor Raytchev" <[EMAIL PROTECTED]> wrote:
> Hello everybody,
>
> After Marc Fournier commented, it is time for pgaccess.org to make a
> decision.
>
> It is clear the project needs the following tools.
>
> - web site
> - mailing list(s)
> - cvs
> - bug track
Hello everybody,
After Marc Fournier commented, it is time for pgaccess.org to make a
decision.
It is clear the project needs the following tools.
- web site
- mailing list(s)
- cvs
- bug tracking system
It is clear, that there is a small new group with fresh desire to contribute
in a dedicate
13 matches
Mail list logo
