List traffic
in [PgSql]
|
Prev: Patch for PKST timezone
Next: [HACKERS] SHARE locks vs. DELETE in SERIALIZABLE mode (Was: Partitioning/inherited tables vs FKs)
From: Bruce Momjian on 11 May 2010 09:50 Simon Riggs wrote: > > Traffic on the PostgreSQL lists is very high now and I freely admit that > reading every email is simply not possible for me, even the ones that > mention topics that keyword searches tell me are of potential interest. > > If anybody knows of a bug or suspected bug in my code, I have no problem > in being copied in on mails so that I can see the issues exist. I do not > promise to respond to every mail I'm copied on, though, but it at least > helps me manage the fire hydrant. [ email only to hackers; admin and general email lists removed ] I completely understand the problem of keeping up with the email lists. Because you are a committer, I hope you will be able to monitor post-commit feedback for patches you apply. Other than that, I can collect bug reports related to your work and ask you to review a web page occasionally. However, it is hard to do this during beta because the bugs usually need to be addressed quickly. -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.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: "Marc G. Fournier" on 11 May 2010 09:58 On Tue, 11 May 2010, Bruce Momjian wrote: > Simon Riggs wrote: >> >> Traffic on the PostgreSQL lists is very high now and I freely admit that >> reading every email is simply not possible for me, even the ones that >> mention topics that keyword searches tell me are of potential interest. >> >> If anybody knows of a bug or suspected bug in my code, I have no problem >> in being copied in on mails so that I can see the issues exist. I do not >> promise to respond to every mail I'm copied on, though, but it at least >> helps me manage the fire hydrant. > > [ email only to hackers; admin and general email lists removed ] > > I completely understand the problem of keeping up with the email lists. > Because you are a committer, I hope you will be able to monitor > post-commit feedback for patches you apply. Other than that, I can > collect bug reports related to your work and ask you to review a web > page occasionally. However, it is hard to do this during beta because > the bugs usually need to be addressed quickly. If list traffic, especially on -hackers, is getting so large, should we look at maybe splitting it? I could easily enough split things such that I duplicate the subscriber list, so nobody would have to subscribe, but it would make it easier for ppl to filter their incoming ... ? Not sure where the split would be, mind you ... almost thinking about patch review / discussions vs hashing out new features or something like that ... Just a thought ... ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- 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: Magnus Hagander on 11 May 2010 10:06 On Tue, May 11, 2010 at 3:58 PM, Marc G. Fournier <scrappy(a)hub.org> wrote: > On Tue, 11 May 2010, Bruce Momjian wrote: > >> Simon Riggs wrote: >>> >>> Traffic on the PostgreSQL lists is very high now and I freely admit that >>> reading every email is simply not possible for me, even the ones that >>> mention topics that keyword searches tell me are of potential interest. >>> >>> If anybody knows of a bug or suspected bug in my code, I have no problem >>> in being copied in on mails so that I can see the issues exist. I do not >>> promise to respond to every mail I'm copied on, though, but it at least >>> helps me manage the fire hydrant. >> >> [ email only to hackers; admin and general email lists removed ] >> >> I completely understand the problem of keeping up with the email lists. >> Because you are a committer, I hope you will be able to monitor >> post-commit feedback for patches you apply. Other than that, I can >> collect bug reports related to your work and ask you to review a web >> page occasionally. However, it is hard to do this during beta because >> the bugs usually need to be addressed quickly. > > If list traffic, especially on -hackers, is getting so large, should we look at maybe splitting it? I could easily enough split things such that I duplicate the subscriber list, so nobody would have to subscribe, but it would make it easier for ppl to filter their incoming ... ? Can we *PLEASE* not go down that route again? We already have way too many lists. Making more of them will just make things more annoying, because people will just end up crossposting everywhere so people don't miss it. There are good client-side (or cloud-side) tools to handle priorities, etc, that works much better. > Not sure where the split would be, mind you ... almost thinking about patch review / discussions vs hashing out new features or something like that .... We just *discontinued* -patches. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.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: Simon Riggs on 11 May 2010 10:10 On Tue, 2010-05-11 at 09:50 -0400, Bruce Momjian wrote: > Simon Riggs wrote: > > > > Traffic on the PostgreSQL lists is very high now and I freely admit that > > reading every email is simply not possible for me, even the ones that > > mention topics that keyword searches tell me are of potential interest. > > > > If anybody knows of a bug or suspected bug in my code, I have no problem > > in being copied in on mails so that I can see the issues exist. I do not > > promise to respond to every mail I'm copied on, though, but it at least > > helps me manage the fire hydrant. > > [ email only to hackers; admin and general email lists removed ] > > I completely understand the problem of keeping up with the email lists. > Because you are a committer, I hope you will be able to monitor > post-commit feedback for patches you apply. Other than that, I can > collect bug reports related to your work and ask you to review a web > page occasionally. However, it is hard to do this during beta because > the bugs usually need to be addressed quickly. Thanks. I have already been keeping a public known bugs/issues list for more than a year. I do monitor for post-commit feedback, though reading all emails isn't always possible when I'm working on resolving current bugs. -- Simon Riggs www.2ndQuadrant.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: Bruce Momjian on 11 May 2010 10:23
Simon Riggs wrote: > On Tue, 2010-05-11 at 09:50 -0400, Bruce Momjian wrote: > > Simon Riggs wrote: > > > > > > Traffic on the PostgreSQL lists is very high now and I freely admit that > > > reading every email is simply not possible for me, even the ones that > > > mention topics that keyword searches tell me are of potential interest. > > > > > > If anybody knows of a bug or suspected bug in my code, I have no problem > > > in being copied in on mails so that I can see the issues exist. I do not > > > promise to respond to every mail I'm copied on, though, but it at least > > > helps me manage the fire hydrant. > > > > [ email only to hackers; admin and general email lists removed ] > > > > I completely understand the problem of keeping up with the email lists. > > Because you are a committer, I hope you will be able to monitor > > post-commit feedback for patches you apply. Other than that, I can > > collect bug reports related to your work and ask you to review a web > > page occasionally. However, it is hard to do this during beta because > > the bugs usually need to be addressed quickly. > > Thanks. I have already been keeping a public known bugs/issues list for > more than a year. I do monitor for post-commit feedback, though reading > all emails isn't always possible when I'm working on resolving current > bugs. Sure. You did a huge job of getting HS done and I will try to help where I can, and I know you have a business to run (http://www.2ndquadrant.com/). -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.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 |