bugzilla items not forwarded to this list
I have opened a couple of bugs via the bugzilla.balabit.com system and the bugs have not come through to the mailing list. Evan.
Hi, thanks for noticing this. I've reenabled it, so it should work with the next update. On Sun, 2010-04-11 at 10:28 -0700, Evan Rempel wrote:
I have opened a couple of bugs via the bugzilla.balabit.com system and the bugs have not come through to the mailing list.
Evan. ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
-- Bazsi
On Mon, Apr 12, 2010 at 7:18 AM, Balazs Scheidler <bazsi@balabit.hu> wrote:
Hi,
thanks for noticing this. I've reenabled it, so it should work with the next update.
On Sun, 2010-04-11 at 10:28 -0700, Evan Rempel wrote:
I have opened a couple of bugs via the bugzilla.balabit.com system and the bugs have not come through to the mailing list.
Evan.
______________________________________________________________________________
-- Bazsi
Isn't this a little spammy? Perhaps a "dev" mailing list would be a better outlet. -- Lance Laursen Demonware Systems Engineer
Isn't this a little spammy? Perhaps a "dev" mailing list would be a
I second that idea. A -dev would be the best way to distribute bugzilla ticket status. -C
On Tue, 2010-04-13 at 12:59 -0400, Christopher Barry wrote:
Isn't this a little spammy? Perhaps a "dev" mailing list would be a
I second that idea. A -dev would be the best way to distribute bugzilla ticket status.
Well, is it really that spammy? We had about 80 tickets in the last 2.5 half years. This gateway used to work this way for most of this time, only recently was it broken. I guesstimate that we had at most 300 bugzilla mails in 2.5 years. That's about 1 every 3 days on average. If we push bugzilla to a -dev list, then reports there would get less visibility, making it easier to just send bugreports to the list. Also, I find it useful to know that there's a bug lurking somewhere, even if you are not affected. Nevertheless, I got two comments who supported the idea of creating a separate -dev list, I can do that if need to be. But before doing that I'd like to clarify the aims of the dev list. Apart from bugzilla mail, what discussions should be moved to the dev list? * I frequently post patches here in response to user requests * Sometimes I feel I need to explain some things in response to a user request that describes code (for example: you can find this code here and there, where you can tweak it) Currently I don't feel that the list traffic is overwhelming (10-15 messages daily) and until it becomes irritating I would vote against separating discussions to a separate -dev list. What I saw in other projects, is that this separation is performed when the number of support questions become so large that developers would prefer to ignore that, and I wouldn't want to move off the "user" list. So what is your opinion? Please respond 1) create a separate "dev" list as proposed and keep the current list for user questions 2) create a separate "bugs" list, only to have bugzilla mail 3) don't do anything, bugzilla mail is fine here 4) stop bugzilla mail altogether I would propose #3 right now and we had two suggestion for #1, but I'd like to gather more opinions in the light of the questions I've asked here. I've set up a simple doodle based poll here: http://www.doodle.com/mn68mrc5977skwsd Please respond there, so it is easier to collect the responses. Lance, Christopher, please also add your opinion to the Doodle poll. Thanks. -- Bazsi
On Wed, 2010-04-14 at 21:57 +0200, Balazs Scheidler wrote:
On Tue, 2010-04-13 at 12:59 -0400, Christopher Barry wrote:
Isn't this a little spammy? Perhaps a "dev" mailing list would be a
I second that idea. A -dev would be the best way to distribute bugzilla ticket status.
Well, is it really that spammy? We had about 80 tickets in the last 2.5 half years. This gateway used to work this way for most of this time, only recently was it broken.
I guesstimate that we had at most 300 bugzilla mails in 2.5 years. That's about 1 every 3 days on average.
If we push bugzilla to a -dev list, then reports there would get less visibility, making it easier to just send bugreports to the list. Also, I find it useful to know that there's a bug lurking somewhere, even if you are not affected.
Nevertheless, I got two comments who supported the idea of creating a separate -dev list, I can do that if need to be. But before doing that I'd like to clarify the aims of the dev list.
Apart from bugzilla mail, what discussions should be moved to the dev list?
* I frequently post patches here in response to user requests * Sometimes I feel I need to explain some things in response to a user request that describes code (for example: you can find this code here and there, where you can tweak it)
Currently I don't feel that the list traffic is overwhelming (10-15 messages daily) and until it becomes irritating I would vote against separating discussions to a separate -dev list.
What I saw in other projects, is that this separation is performed when the number of support questions become so large that developers would prefer to ignore that, and I wouldn't want to move off the "user" list.
So what is your opinion? Please respond
1) create a separate "dev" list as proposed and keep the current list for user questions 2) create a separate "bugs" list, only to have bugzilla mail 3) don't do anything, bugzilla mail is fine here 4) stop bugzilla mail altogether
I would propose #3 right now and we had two suggestion for #1, but I'd like to gather more opinions in the light of the questions I've asked here.
I've set up a simple doodle based poll here:
http://www.doodle.com/mn68mrc5977skwsd
Please respond there, so it is easier to collect the responses. Lance, Christopher, please also add your opinion to the Doodle poll. Thanks.
So far we have 11 votes for option #3 above (and no votes for any other options). I know it's been only a day, but I'd like to close this question tomorrow. So if you have a different opinion, it is now time to voice it! -- Bazsi
On Thu, 2010-04-15 at 21:13 +0200, Balazs Scheidler wrote:
On Wed, 2010-04-14 at 21:57 +0200, Balazs Scheidler wrote:
On Tue, 2010-04-13 at 12:59 -0400, Christopher Barry wrote:
Isn't this a little spammy? Perhaps a "dev" mailing list would be a
I second that idea. A -dev would be the best way to distribute bugzilla ticket status.
Well, is it really that spammy? We had about 80 tickets in the last 2.5 half years. This gateway used to work this way for most of this time, only recently was it broken.
I guesstimate that we had at most 300 bugzilla mails in 2.5 years. That's about 1 every 3 days on average.
If we push bugzilla to a -dev list, then reports there would get less visibility, making it easier to just send bugreports to the list. Also, I find it useful to know that there's a bug lurking somewhere, even if you are not affected.
Nevertheless, I got two comments who supported the idea of creating a separate -dev list, I can do that if need to be. But before doing that I'd like to clarify the aims of the dev list.
Apart from bugzilla mail, what discussions should be moved to the dev list?
* I frequently post patches here in response to user requests * Sometimes I feel I need to explain some things in response to a user request that describes code (for example: you can find this code here and there, where you can tweak it)
Currently I don't feel that the list traffic is overwhelming (10-15 messages daily) and until it becomes irritating I would vote against separating discussions to a separate -dev list.
What I saw in other projects, is that this separation is performed when the number of support questions become so large that developers would prefer to ignore that, and I wouldn't want to move off the "user" list.
So what is your opinion? Please respond
1) create a separate "dev" list as proposed and keep the current list for user questions 2) create a separate "bugs" list, only to have bugzilla mail 3) don't do anything, bugzilla mail is fine here 4) stop bugzilla mail altogether
I would propose #3 right now and we had two suggestion for #1, but I'd like to gather more opinions in the light of the questions I've asked here.
I've set up a simple doodle based poll here:
http://www.doodle.com/mn68mrc5977skwsd
Please respond there, so it is easier to collect the responses. Lance, Christopher, please also add your opinion to the Doodle poll. Thanks.
So far we have 11 votes for option #3 above (and no votes for any other options). I know it's been only a day, but I'd like to close this question tomorrow.
So if you have a different opinion, it is now time to voice it!
If the hiccup just did a dump all at once, and that is completely out of the ordinary, and the volume is negligible, then the visibility to all list members is worth it. I recant and opt for #3 as well. -C
If the hiccup just did a dump all at once, and that is completely out of the ordinary, and the volume is negligible, then the visibility to all list members is worth it. I recant and opt for #3 as well.
-C
Ditto, I made the 'spammy' comment after seeing 8 nearly consecutive bug emails right after it was mentioned that relaying bugs to the list would be turned back on. I've since filtered out [Bug *, so I rescind regardless. -- Lance Laursen Demonware Systems Engineer
On Thu, 2010-04-15 at 14:38 -0700, Lance Laursen wrote:
If the hiccup just did a dump all at once, and that is completely out of the ordinary, and the volume is negligible, then the visibility to all list members is worth it. I recant and opt for #3 as well.
-C
Ditto, I made the 'spammy' comment after seeing 8 nearly consecutive bug emails right after it was mentioned that relaying bugs to the list would be turned back on. I've since filtered out [Bug *, so I rescind regardless.
Hi, I'm closing the poll with the result that everything stays as it was, e.g. bug emails are gatewayed to the list. -- Bazsi
participants (4)
-
Balazs Scheidler
-
Christopher Barry
-
Evan Rempel
-
Lance Laursen