Re: PostgreSQL 8.4 development plan

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, Dave Page <dpage(at)postgresql(dot)org>
Subject: Re: PostgreSQL 8.4 development plan
Date: 2008-02-07 17:53:38
Message-ID: 20080207175338.GP26016@yugib.highrise.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Josh,

Try it out. Setup a review-board installation, point it at your SVN
mirror. As long as people can "post" diffs (and from the the
screenshots, it looks like it has a "diff file" browse button), it
doesnt' really matter what "it" uses as it's backend, does it?

And if it turns out to be a good means for discussion patches, or at
lease "recording" patches and status, then good.

And the nice thing is that it could even be "managed" by observers at
first, much like the wiki patch status page was until it's been shown
(if it is) to be a good tool for tracking patches, etc.

I'm slightly wary of it, but that's probably just because my normal
development work-flow *doesn't* include a web-browser for anything, and
being forced to use some AJAXy web-interface to do/see anything probably
means I won't do/see anything... Thankfully, my absence in the
development process isn't something that the PostgreSQL community will
greatly miss...

a.

* Joshua D. Drake <jd(at)commandprompt(dot)com> [080207 11:46]:

> > The point I tried to make earlier was that if we actually started to
> > rely on such a tool, we'd want to fix it to talk to CVS. Hey, it's
> > an open source project, right?
>
> Yes but we are supposed to work smart not hard. CVS doesn't fit that
> criteria when we have highly available, highly used and highly trusted
> options available. We even have an option with an extremely low barrier
> of entry (svn) and options that are proven amongst one of the (if not
> the) most active FOSS projects on the planet (git).
>
> I am not arguing any particular solution but home brewing a solution so
> people can stay on what is definitely a dying SCM is dumb. There are
> so many tools available to us that we *don't* have to modify, bend,
> break or if you like, improve that any argument outside of, "We are
> used to CVS" is just hand waving and that argument is sad.
>
> Sincerely,
>
> Joshua D. Drake
>
> --
> The PostgreSQL Company since 1997: http://www.commandprompt.com/
> PostgreSQL Community Conference: http://www.postgresqlconference.org/
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
>

--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jignesh K. Shah 2008-02-07 17:57:28 Re: Why are we waiting?
Previous Message Magnus Hagander 2008-02-07 17:48:15 Re: PostgreSQL 8.4 development plan