How about closing some Open Items?
in [PgSql]
|
From: Tom Lane on 8 Jun 2010 15:46 Josh Berkus <josh(a)agliodbs.com> writes: > Let's get 9.0 out the door, hey? What we actually need is some testing effort. The lack of bug reports against Hot Standby, in particular, is proof positive that no meaningful testing is happening. (If you think it means HS is bug-free, I have a nice bridge I'd like to interest you in.) regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Josh Berkus on 8 Jun 2010 17:13 On 6/8/10 2:01 PM, Robert Haas wrote: > I appreciate the effort that went into making this list, but it's not > very useful to work off of any more. The problem is that the set of > things that is listed here is pretty erratic - there are actual > problems that are not on this list, and there are things on this list > that are 100% unimportant. So? Improve the quality of the list then. Bashing the quality of another community member's efforts is not at all helpful, and certainly does nothing to move us towards 9.0. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: David Fetter on 8 Jun 2010 17:29 On Tue, Jun 08, 2010 at 03:46:06PM -0400, Tom Lane wrote: > Josh Berkus <josh(a)agliodbs.com> writes: > > Let's get 9.0 out the door, hey? > > What we actually need is some testing effort. The lack of bug > reports against Hot Standby, in particular, is proof positive that > no meaningful testing is happening. (If you think it means HS is s/HS/any software, no matter how trivial/ > bug-free, I have a nice bridge I'd like to interest you in.) Is it the one from Lower Manhattan to Brooklyn? I've got all kinds of cool ideas about what to do with it... Cheers, David. -- David Fetter <david(a)fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter(a)gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Josh Berkus on 8 Jun 2010 18:20 > Whoa, there. There is not any way of moving forward with this list > without explaining why the list in its present form is not too useful. Ah, the way I read your post was "the list is not useful therefore I will ignore it." From that perspective it was important for me to respond to you lest other hackers make the same excuse to ignore the open items list. So, miscommunication over! > If I simply start overhauling the list without explaining what I > perceive to be the systematic problems with it, then I will get yelled > at for failing to follow community process. Nonsense. The one good thing about admin stuff in this community is since nobody wants to do it, you seldom get critiqued for how you did it. ;-) > So I agree with your statement that we need to improve the quality of > the list, which is why I just spent three hours working on the items > where I could discern a clear action item as well as doing some > cleanup. Like most PG hackers, I am extremely busy, which is why I > would appreciate any help that you or any other community member would > care to offer to help get the list cleaned up. Yeah, I was going through the list today trying to see if stuff needed to be removed or added, which is why I noticed the almost total lack of movement since the 26th. > Failing that, or in > addition, I would appreciate feedback on what I believe to be a > legitimate complaint about the documentation items on the list, > namely, that they're mostly unimportant things that should probably > just be dropped unless or until the people who originally raised the > issues feel like pursuing them. Well, if something is too trivial to be worth fixing, that's a reason to remove it. > I am trying to solve a problem, not pick a fight. I responded to your > original post on this topic by dropping what I was planning to do this > afternoon to work on this, and I'd like a few brownie points for that. Brownie points granted. Although I'd think actual brownies or cookies would be better. ;-) -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 8 Jun 2010 17:43 On Tue, Jun 8, 2010 at 5:13 PM, Josh Berkus <josh(a)agliodbs.com> wrote: > On 6/8/10 2:01 PM, Robert Haas wrote: >> I appreciate the effort that went into making this list, but it's not >> very useful to work off of any more. �The problem is that the set of >> things that is listed here is pretty erratic - there are actual >> problems that are not on this list, and there are things on this list >> that are 100% unimportant. > > So? �Improve the quality of the list then. �Bashing the quality of > another community member's efforts is not at all helpful, and certainly > does nothing to move us towards 9.0. Whoa, there. There is not any way of moving forward with this list without explaining why the list in its present form is not too useful. If I simply start overhauling the list without explaining what I perceive to be the systematic problems with it, then I will get yelled at for failing to follow community process. On the other hand, if I point out the problem, apparently that's bashing another community member. I attempted to avoid that pitfall by saying "I appreciate the effort that went into making this list" (because I do) and I tried to make it clear that I felt it had been useful at one point by saying "any more". The fact that the list is not as useful now is not because Selena sucks (she doesn't, by the way! - Hi Selena!) but because Selena overhauled this list on the 19th of May and cleaned it up some more on the 26th, and it's now the 8th of June, and not enough systematic effort has been put into keeping it up to date. It's not Selena's job to keep the list up to date, but it's a fact of life that if neither she nor anyone else does, it's going to become less useful. So I agree with your statement that we need to improve the quality of the list, which is why I just spent three hours working on the items where I could discern a clear action item as well as doing some cleanup. Like most PG hackers, I am extremely busy, which is why I would appreciate any help that you or any other community member would care to offer to help get the list cleaned up. Failing that, or in addition, I would appreciate feedback on what I believe to be a legitimate complaint about the documentation items on the list, namely, that they're mostly unimportant things that should probably just be dropped unless or until the people who originally raised the issues feel like pursuing them. I am trying to solve a problem, not pick a fight. I responded to your original post on this topic by dropping what I was planning to do this afternoon to work on this, and I'd like a few brownie points for that. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
|
Next
|
Last
Pages: 1 2 3 Prev: _bt_parent_deletion_safe() isn't safe Next: Command to prune archive at restartpoints |