On Sat, 9 Feb 2008, Jan Wieck wrote:
It is pretty obvious that amost every current system has options to
convert from or to mirror a CVS repository. But what if we someday
really want to use something else as the master repository?
In order to export from CVS into one of the newer systems, th
On Feb 10, 2008 8:58 AM, Jan Wieck <[EMAIL PROTECTED]> wrote:
> I wonder if the efforts to provide mirrors for many different systems can
> hurt later down the road. It is pretty obvious that amost every current
> system has options to convert from or to mirror a CVS repository. But what if
> we
-Original Message-
From: Peter Eisentraut <[EMAIL PROTECTED]>
Subj: Re: [HACKERS] PostgreSQL 8.4 development plan
Date: Fri Feb 8, 2008 7:15
Size: 773 bytes
To: "Brendan Jurd" <[EMAIL PROTECTED]>
cc: "Markus Bertheau" <[EMAIL PROTECTED]>; pgsql-hacker
Andrew Dunstan escribió:
>
> Joshua D. Drake wrote:
Can you document what you actually do on the developers' wiki?
>>> I'd prefer we do not advertise it until it's actually usable.
>>
>> Wait, what are we talking about? The SVN mirror we have right now is
>> perfectly usable.
Joshua D. Drake wrote:
Can you document what you actually do on the developers' wiki?
I'd prefer we do not advertise it until it's actually usable.
Wait, what are we talking about? The SVN mirror we have right now is
perfectly usable. It just has to be rebuilt a couple of time
Joshua D. Drake wrote:
On Fri, 8 Feb 2008 12:39:36 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Andrew Dunstan escribió:
Alvaro Herrera wrote:
Florian Pflug escribió:
Yeah, the SVN mirror in commandprompt.com is recreated from scratch
every time. This sucks, we know -- I think it's on Jo
On Fri, 8 Feb 2008 12:39:36 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Andrew Dunstan escribió:
>
> > Alvaro Herrera wrote:
> >> Florian Pflug escribió:
>
> >> Yeah, the SVN mirror in commandprompt.com is recreated from scratch
> >> every time. This sucks, we know -- I think it's on Josh
Andrew Dunstan escribió:
> Alvaro Herrera wrote:
>> Florian Pflug escribió:
>> Yeah, the SVN mirror in commandprompt.com is recreated from scratch
>> every time. This sucks, we know -- I think it's on Joshua's list to
>> change it to update incrementally.
>
> Can you document what you actually
On Fri, 08 Feb 2008 10:25:33 -0500
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> > Yeah, the SVN mirror in commandprompt.com is recreated from scratch
> > every time. This sucks, we know -- I think it's on Joshua's list to
> > change it to update incrementally.
> >
> >
>
> Can you document wha
Alvaro Herrera wrote:
Florian Pflug escribió:
I've tried with both the SVN and the GIT mirror. Things worked well
initialled, but in *both* cases pulling changes from the mirror stopped
working after a few weeks or so. It seems that both of these mirrors
create the SVN/GIT repo from s
Tom Lane wrote:
Dimitri Fontaine <[EMAIL PROTECTED]> writes:
Le Wednesday 06 February 2008 21:35:54 Peter Eisentraut, vous avez écrit :
Yes, I feel we could use a group writeable patch queue of some sort.
Perhaps an IMAP server setup could do the job.
I've read some developers appreciating t
* Florian Pflug <[EMAIL PROTECTED]> [080208 09:25]:
> Aidan Van Dyk wrote:
> >The Git repo certainly is an "incremental" update.
> >
> >If you ever see a "rewind" (non-fastforward) of the the repo.or.cz
> >PostgreSQL repo, please let me know...
>
> Hm... interesting...
>
> I'm pretty sure that th
Aidan Van Dyk wrote:
The Git repo certainly is an "incremental" update.
If you ever see a "rewind" (non-fastforward) of the the repo.or.cz
PostgreSQL repo, please let me know...
Hm... interesting...
I'm pretty sure that the "past" changed at least once - at least I once
got loud complaints f
Florian Pflug escribió:
> I've tried with both the SVN and the GIT mirror. Things worked well
> initialled, but in *both* cases pulling changes from the mirror stopped
> working after a few weeks or so. It seems that both of these mirrors
> create the SVN/GIT repo from scratch every time the
The Git repo certainly is an "incremental" update.
If you ever see a "rewind" (non-fastforward) of the the repo.or.cz
PostgreSQL repo, please let me know...
a.
* Florian Pflug <[EMAIL PROTECTED]> [080208 07:50]:
> I've tried with both the SVN and the GIT mirror. Things worked well
> initiall
Peter Eisentraut wrote:
Am Freitag, 8. Februar 2008 schrieb Brendan Jurd:
In particular, if the git repos were officially supported, and best
practises for use with Postgres documented, I think a lot more hackers
would be comfortable using git to do their work, which is good for
collaboration (a
Am Freitag, 8. Februar 2008 schrieb Brendan Jurd:
> In particular, if the git repos were officially supported, and best
> practises for use with Postgres documented, I think a lot more hackers
> would be comfortable using git to do their work, which is good for
> collaboration (as mentioned by Greg
On Feb 8, 2008 10:29 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Freitag, 8. Februar 2008 schrieb Markus Bertheau:
> > Maybe the existing SVN, git and other mirrors could just become more
> > official and supported in the sense that users can rely on them to be
> > updated often enough?
>
Am Freitag, 8. Februar 2008 schrieb Markus Bertheau:
> Maybe the existing SVN, git and other mirrors could just become more
> official and supported in the sense that users can rely on them to be
> updated often enough?
I think you are right. Some of that is already being worked on. It certainly
2008/2/8, Heikki Linnakangas <[EMAIL PROTECTED]>:
> Gregory Stark wrote:
> > git or its ilk would impact the lives of submitters and reviewers most.
> > Basically it would allow two non-committers to collaborate, something
which we
> > can't really do effectively now.
>
> Two git-using non-committe
On Friday 08 February 2008 00:52:04 Gregory Stark wrote:
> Well not really. Our current model is that only stuff that's ready for
> widespread use goes into CVS. That means "everything" isn't open and shared
> at all. "everything" is mostly sitting on people's local hard drives where
> you can't u
Gregory Stark wrote:
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
Therefore, we can provide mirrors of the CVS repository in multiple formats.
And those mirrors exist already, I remember a GIT and a Subversion mirror off
the top of my head, and I bet there's others. After we have that, the
Magnus Hagander wrote:
Alvaro Herrera wrote:
Stefan Kaltenbrunner escribió:
yeah - the test install is available on
http://reviewdemo.postgresql.org if people want to test judge for
themself - contact magnus or me if you need permissions to do/test
stuff there.
Thanks. I tried submittin
Christopher Browne wrote:
On Feb 7, 2008 9:42 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Gregory Stark escribió:
For what it's worth I think GIT is a better fit for our needs.
Perhaps it would be, if it worked on Windows ... Not that I care, but I
bet Magnus would.
http://code.google.com
"Fabien COELHO" <[EMAIL PROTECTED]> writes:
> ISTM that a decentralized or distributed SCM for PostgreSQL would be a bad
> move, however great it would be at branching and merging. For me it is a
> philosophy question: if PGSQL is a "common work", then everything should be
> open and shared, and
Alvaro Herrera wrote:
Stefan Kaltenbrunner escribió:
yeah - the test install is available on http://reviewdemo.postgresql.org
if people want to test judge for themself - contact magnus or me if you
need permissions to do/test stuff there.
Thanks. I tried submitting a review request agains
On Feb 7, 2008 9:42 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Gregory Stark escribió:
>
> > For what it's worth I think GIT is a better fit for our needs.
>
> Perhaps it would be, if it worked on Windows ... Not that I care, but I
> bet Magnus would.
http://code.google.com/p/msysgit/
"Unfor
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Therefore, we can provide mirrors of the CVS repository in multiple formats.
> And those mirrors exist already, I remember a GIT and a Subversion mirror off
> the top of my head, and I bet there's others. After we have that, the master
> version c
Stefan Kaltenbrunner escribió:
> yeah - the test install is available on http://reviewdemo.postgresql.org
> if people want to test judge for themself - contact magnus or me if you
> need permissions to do/test stuff there.
Thanks. I tried submitting a review request against anoncvs but it
fa
Fabien COELHO wrote:
> I'm not sure I would be proud to use such a stupidly named tool for a
> "common work". I really do not share Linus humor, and apparent contempt
> for other people. GIT implements "I want to chose whom I work with, and
> don't care about the others, and don't ever want to h
Fabien COELHO wrote:
ISTM that a decentralized or distributed SCM for PostgreSQL would be a
bad move, however great it would be at branching and merging. For me
it is a philosophy question: if PGSQL is a "common work", then
everything should be open and shared, and a centralized systems make
Alvaro Herrera wrote:
Gregory Stark escribió:
For what it's worth I think GIT is a better fit for our needs.
Perhaps it would be, if it worked on Windows ... Not that I care, but I
bet Magnus would.
There's fairly good tools to convert from one version control system to
another. Especially
Mark Mielke wrote:
Perhaps he didn't read the instructions. See below for a 5 minutes 34
elapsed time. This includes extracting SVN over the network using SVN.
And just to be complete, here is git at 2 minutes 13 seconds. Not that
these times matter at all, but in case anybody thinks they do..
Peter Eisentraut wrote:
Am Donnerstag, 7. Februar 2008 schrieb Tom Lane:
So, again, the question is has anyone really used it? Is it the
best thing since sliced bread, or not so much?
I think it is about the equivalent of replacing a mailing list by Yahoo
Groups. It has more special effects
Dear Mark,
I encourage all to keep their minds open.
Good:-)
My 0.02 EUR (or even less) on the recurrent SCM flame war on the list.
ISTM that a decentralized or distributed SCM for PostgreSQL would be a bad
move, however great it would be at branching and merging. For me it is a
philosop
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
I'm not sure we're talking about the same thing. I've never heard any
complaints about building svn from source before for *developers*. I think
that's just as easy as anything else.
[ shrug... ] The message I quoted was from
Alvaro Herrera wrote:
Gregory Stark escribió:
For what it's worth I think GIT is a better fit for our needs.
Perhaps it would be, if it worked on Windows ... Not that I care, but I
bet Magnus would.
To summarize what I care about: I don't really care if I can't *commit*
from Windows - I n
On Feb 7, 2008 9:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> At the very least, I suggest you replicate the experiment before
> asserting you know more about it than someone who's tried.
Will you accept the testimony of someone who has built an SVN *server*
entirely from source on Slackware Linu
Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
I'm not sure we're talking about the same thing. I've never heard any
complaints about building svn from source before for *developers*. I think
that's just as easy as anything else.
[ shrug... ] The message I quoted was from Bob Frie
On Thu, 7 Feb 2008, Tom Lane wrote:
Subversion - 4-6 hours (depends on a multitude of packages and will
only work with specific versions which you
learn about the hard way at build time).
I have seen one of these nightmare Subversion installs b
Gregory Stark escribió:
> For what it's worth I think GIT is a better fit for our needs.
Perhaps it would be, if it worked on Windows ... Not that I care, but I
bet Magnus would.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prom
Gregory Stark <[EMAIL PROTECTED]> writes:
> I'm not sure we're talking about the same thing. I've never heard any
> complaints about building svn from source before for *developers*. I think
> that's just as easy as anything else.
[ shrug... ] The message I quoted was from Bob Friesenhahn, who i
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Mark Mielke <[EMAIL PROTECTED]> writes:
>> In terms of picking an SCM candidate, I don't think "time to install
>> from source" is a legitimate concern. Installing from source is great,
>> but if the package needs to be installed from source, it is not we
Am Donnerstag, 7. Februar 2008 schrieb Tom Lane:
> So, again, the question is has anyone really used it? Is it the
> best thing since sliced bread, or not so much?
I think it is about the equivalent of replacing a mailing list by Yahoo
Groups. It has more special effects, and no doubt some peop
Joshua D. Drake wrote:
On Thu, 7 Feb 2008 14:00:33 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Joshua D. Drake escribió:
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
Tom Lane wrote:
Mark Mielke <[EMAIL PROTECTED]> writes:
In terms of picking an SCM candidate, I don't think "time to install
from source" is a legitimate concern. Installing from source is great,
but if the package needs to be installed from source, it is not well
enough supported by the co
Dimitri Fontaine wrote:
Le Thursday 07 February 2008 17:19:26 Tom Lane, vous avez écrit :
Not having looked into exactly how it works and if it's something we
want, but if we want to, any reason we can't just point it at the svn
mirror?
Synchronization problems scare me.
AIUI we're talking ab
Le Thursday 07 February 2008 17:19:26 Tom Lane, vous avez écrit :
> > Not having looked into exactly how it works and if it's something we
> > want, but if we want to, any reason we can't just point it at the svn
> > mirror?
>
> Synchronization problems scare me.
AIUI we're talking about one way s
Mark Mielke <[EMAIL PROTECTED]> writes:
> In terms of picking an SCM candidate, I don't think "time to install
> from source" is a legitimate concern. Installing from source is great,
> but if the package needs to be installed from source, it is not well
> enough supported by the community to be
Tom Lane wrote:
From a relative time to install from source standpoint it looks like
this:
CVS- 10 minutes (no external dependencies)
GIT- 8 minutes (no external dependencies)
Mercurial - 1 minute (depends on Python)
Subversion - 4-6 hours (depends on a multitude of packag
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> I repeat. I am not arguing a particular solution. I am arguing against
> creating more internal infrastructure and the relevant support
> requirements when other solutions exist.
Who said anything about internal infrastructure? We'd be helping
anoth
Joshua D. Drake wrote:
On Thu, 7 Feb 2008 14:00:33 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Joshua D. Drake escribió:
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
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 g
On Thu, 7 Feb 2008 14:00:33 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake escribió:
>
> > 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
Joshua D. Drake escribió:
> 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
On Thu, 07 Feb 2008 11:19:26 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > On Wed, Feb 06, 2008 at 06:50:34PM -0500, Tom Lane wrote:
> >> Hmm, the info on that last page might be out of date, but what it
> >> says is that the only SCMS they really supp
Magnus Hagander <[EMAIL PROTECTED]> writes:
> On Wed, Feb 06, 2008 at 06:50:34PM -0500, Tom Lane wrote:
>> Hmm, the info on that last page might be out of date, but what it says is
>> that the only SCMS they really support 100% is SVN. The other ones they
>> claim support for don't work [well/at a
James Mansion <[EMAIL PROTECTED]> writes:
> The curre nt *plan* is for a 14 month cycle. And it will probably
> slip. Some of the queued items are going to be very old by the time
> you go to 8.4 on this program, which seems a shame.
What? The plan is to deal with them next month (in the first
Andrew Dunstan wrote:
Stefan Kaltenbrunner wrote:
I could do a demo install on the trackerdemo jail - that one seems to
have most of the prequisits and would not need work to get going. Not
sure I want to install MySQL there though - so we would have to go
with the sqlite backend for the t
Stefan Kaltenbrunner wrote:
I could do a demo install on the trackerdemo jail - that one seems to
have most of the prequisits and would not need work to get going. Not
sure I want to install MySQL there though - so we would have to go
with the sqlite backend for the test ;-)
Umm, we ne
Magnus Hagander wrote:
On Wed, Feb 06, 2008 at 06:50:34PM -0500, Tom Lane wrote:
Dimitri Fontaine <[EMAIL PROTECTED]> writes:
Le Wednesday 06 February 2008 21:35:54 Peter Eisentraut, vous avez �crit�:
Yes, I feel we could use a group writeable patch queue of some sort.
Perhaps an IMAP server s
On Wed, Feb 06, 2008 at 06:50:34PM -0500, Tom Lane wrote:
> Dimitri Fontaine <[EMAIL PROTECTED]> writes:
> > Le Wednesday 06 February 2008 21:35:54 Peter Eisentraut, vous avez �crit�:
> >> Yes, I feel we could use a group writeable patch queue of some sort.
> >> Perhaps an IMAP server setup could
Le jeudi 07 février 2008, Tom Lane a écrit :
> Hmm, the info on that last page might be out of date, but what it says is
> that the only SCMS they really support 100% is SVN. The other ones they
> claim support for don't work [well/at all] with the post-review tool.
Maybe this is all to naive to
Tom Lane wrote:
There is, although I think a large fraction of it will get bounced as
"needs more work", which should reduce the pressure. We'll just be
trying to give feedback to let the patch authors move forward, which
will not take as much time as actually committing would take.
The current
Tom Lane wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > Just thinking that we'll need somewhere to park the new patches which
> > roll in during a commit fest.
>
> Bruce has always kept two patch queues, one for the current version and
> one for the stuff held for the next version. This
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
O.k. I am not too interested in starting a whole war here (again) but
for the record, we have what appears to be a perfectly working
capability to move from cvs to svn. So *if* review board is something
we really like, the SCM shou
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> O.k. I am not too interested in starting a whole war here (again) but
> for the record, we have what appears to be a perfectly working
> capability to move from cvs to svn. So *if* review board is something
> we really like, the SCM should not be the
On Wed, 06 Feb 2008 18:50:34 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> > I've read some developers appreciating the way review board works:
> > http://review-board.org/
> > http://code.google.com/p/reviewboard/
> > http://code.google.com/p/reviewboard/wiki/UserBasics
>
> Hmm, the info on
Dimitri Fontaine <[EMAIL PROTECTED]> writes:
> Le Wednesday 06 February 2008 21:35:54 Peter Eisentraut, vous avez écrit :
>> Yes, I feel we could use a group writeable patch queue of some sort.
>> Perhaps an IMAP server setup could do the job.
> I've read some developers appreciating the way revi
On Wed, 6 Feb 2008, Magnus Hagander wrote:
Is it technically possible to set permissions on a per-page basis?
Technically possible? Of course. It's sure not easy to do, though; the
Mediawiki team considers having any real ACL structure added onto their
code a non-feature and last time I ch
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Josh Berkus escribió:
I think we might want to do something along the lines of what Stefan set
up (at least I think it was he) for the end of 8.4 on
developer.postgresql.org. Bruce's patch list is easy to update, but hard
to read. I'
On Wed, 06 Feb 2008 22:07:06 +0100
Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > On Wed, 06 Feb 2008 15:46:22 -0500
> > Tom Lane <[EMAIL PROTECTED]> wrote:
> >
> >> Seems like a wiki page with links to pgsql-patches archive entries
> >> would be easy. But an issue for
Le Wednesday 06 February 2008 21:35:54 Peter Eisentraut, vous avez écrit :
> Alvaro Herrera wrote:
> > Easy to update for Bruce -- for anyone else it is impossible to update
> > AFAIK.
>
> Yes, I feel we could use a group writeable patch queue of some sort.
> Perhaps an IMAP server setup could do
Joshua D. Drake wrote:
On Wed, 06 Feb 2008 15:46:22 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
Seems like a wiki page with links to pgsql-patches archive entries
would be easy. But an issue for any of this is who has permissions
to edit the queue? I concur that "Bruce only" is the wrong answe
On Wed, 06 Feb 2008 15:46:22 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Seems like a wiki page with links to pgsql-patches archive entries
> would be easy. But an issue for any of this is who has permissions
> to edit the queue? I concur that "Bruce only" is the wrong answer,
> but I'm not sur
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Josh Berkus escribió:
>>> I think we might want to do something along the lines of what Stefan set
>>> up (at least I think it was he) for the end of 8.4 on
>>> developer.postgresql.org. Bruce's patch list is easy to update, but hard
>>> to read. I'l
On Feb 6, 2008 9:56 AM, Dave Page <[EMAIL PROTECTED]> wrote:
> Whenever a commit fest is in progress, the
> focus will shift from development to review, feedback and commit of
> patches. Each fest will continue until all patches in the queue have
> either been committed to the CVS repository, retur
Alvaro Herrera wrote:
> Josh Berkus escribió:
> > I think we might want to do something along the lines of what Stefan set
> > up (at least I think it was he) for the end of 8.4 on
> > developer.postgresql.org. Bruce's patch list is easy to update, but hard
> > to read. I'll put some effort into i
Josh Berkus escribió:
> I think we might want to do something along the lines of what Stefan set up
> (at least I think it was he) for the end of 8.4 on developer.postgresql.org.
> Bruce's patch list is easy to update, but hard to read. I'll put some effort
> into it.
Easy to update for Bruc
The plan looks great. I am +1
> -Original Message-
> From: [EMAIL PROTECTED]
>
> ---(end of
> broadcast)---
> TIP 4: Have you searched our list archives?
>
>http://archives.postgresql.org
>
---(e
On Wednesday 06 February 2008 09:09, Tom Lane wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > Just thinking that we'll need somewhere to park the new patches which
> > roll in during a commit fest.
>
> Bruce has always kept two patch queues, one for the current version and
> one for the stu
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> we added a March fest in part to have a "practice run" without too much
>> stuff being on the plate.
> OK, that makes some sense, although I don't know about the "not much
> stuff on the plate". We presumably have quite a lot of stuf
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I would rather set a target and modify it if necessary based on
experience than have none at all.
We felt that we'd like to get a couple of fests under our belts before
trying to nail down very many rules. The process will g
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> Just thinking that we'll need somewhere to park the new patches which
> roll in during a commit fest.
Bruce has always kept two patch queues, one for the current version and
one for the stuff held for the next version. This won't change anything
except
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I would rather set a target and modify it if necessary based on
> experience than have none at all.
We felt that we'd like to get a couple of fests under our belts before
trying to nail down very many rules. The process will get more
formalized later,
Dave Page wrote:
On Feb 6, 2008 4:24 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
I would rather set a target and modify it if necessary based on
experience than have none at all.
The danger of not doing so is that we'll be in almost constant 'commit
fest' mode.
Yes, that is somet
On Feb 6, 2008 4:24 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
>
> I would rather set a target and modify it if necessary based on
> experience than have none at all.
>
> The danger of not doing so is that we'll be in almost constant 'commit
> fest' mode.
Yes, that is something we discussed
Dave Page wrote:
On Feb 6, 2008 3:57 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
I would like to see this tied down some more. The time for the commit
fests is too open ended. I think we should say something like "All
commit fests will run no more than two weeks, except for the final
comm
This all sounds very promising.
On Feb 6, 2008 7:56 PM, Dave Page <[EMAIL PROTECTED]> wrote:
> Each fest will continue until all patches in the queue have
> either been committed to the CVS repository, returned to the author
> for additional work, or rejected outright, and until that has
> happene
On Feb 6, 2008 3:57 PM, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
> I would like to see this tied down some more. The time for the commit
> fests is too open ended. I think we should say something like "All
> commit fests will run no more than two weeks, except for the final
> commit fest which c
Am Mittwoch, 6. Februar 2008 schrieb Andrew Dunstan:
> I would like to see this tied down some more. The time for the commit
> fests is too open ended. I think we should say something like "All
> commit fests will run no more than two weeks, except for the final
> commit fest which can run for one
Dave Page wrote:
Hackers,
As you know we've finally released PostgreSQL 8.3, after a development
cycle that lasted well over a year despite our original plans for a 6
month cycle. The core team are aware that there are a number of
factors that contributed to this slippage:
- Lack of prompt an
On Feb 6, 2008 2:44 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> Good start. /me thinks it should be on the website. We've usually announced
> our feature freeze dates there... (in less details, sure, but something
> there)
Feel free - you've been hacking that recently!
/D
On Wed, Feb 06, 2008 at 02:42:35PM +, Dave Page wrote:
> On Feb 6, 2008 1:49 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > On Wed, Feb 06, 2008 at 08:56:51AM +, Dave Page wrote:
> > > Hackers,
> >
> > Looks great and well-thought through. Let's hope it works out!
> >
> > I assume you'l
On Feb 6, 2008 1:49 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 06, 2008 at 08:56:51AM +, Dave Page wrote:
> > Hackers,
>
> Looks great and well-thought through. Let's hope it works out!
>
> I assume you'll be committing this info to the developer section on the
> website?
It'
On Wed, Feb 06, 2008 at 08:56:51AM +, Dave Page wrote:
> Hackers,
Looks great and well-thought through. Let's hope it works out!
I assume you'll be committing this info to the developer section on the
website?
//Magnus
---(end of broadcast)---
On Wed, 2008-02-06 at 08:56 +, Dave Page wrote:
> Hackers,
+1 Very much in favour.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archi
97 matches
Mail list logo
