On 03/12/2024 1:42 PM, Manu wrote:
> I had assumed everybody got the same flood of emails that I got... they did not look like they were 'mine'.

Bugzilla has a bad habit of adding people to tickets when you comment on it.

So you would have interacted with each of the tickets to get the email.

Not everyone got the same number as you.

I only got ~12.

On Monday, December 2, 2024 5:39:11 PM MST Manu via Digitalmars-d-announce wrote:
> I received several hundred emails, and then had to spend ages deleting them
> all... I couldn't select-all because they spanned like 10 pages, and I had
> to de-select the real emails interleaved among them.
> I'm gonna go way out there on the limb and say, I am completely confident
> that nobody wants that.

Personally, I most definitely want that. I keep all such e-mails, and I have e-mail filters which put them in the correct folders. No manual processing is required, and I have all of those e-mails to search through when I need to. I can totally understand that it's annoying to have to manually go through hundreds of e-mails, but e-mail programs provide tools for dealing with that sort of thing, and it's not exactly new that bugzilla e-mails about any comments or changes to bug reports that you're subscribed to. It's just that on this particular occasion, a whole bunch of issues got commented on at once because of the migration. Either way, it's a one time thing (or I guess, a two time thing, since the dmd/druntime issue still need to be moved), and that's the end of it.

For me at least, the annoying part about the messages is that I now have to rework my filters to deal with github sending me e-mails about issues for these repos, and I need to separate those out from e-mails about PRs, whereas before, I could just put all of the e-mails for each repo in a folder for that repo and mostly be able to rely on them all being PR-related e-mails. But that's just life when we change the service we're using for bug reports.

- Jonathan M Davis

On Monday, December 2, 2024 5:45:23 PM MST Richard (Rikki) Andrew Cattermole via Digitalmars-d-announce wrote:
> On 03/12/2024 1:42 PM, Manu wrote:
> > I had assumed everybody got the same flood of emails that I got... they did not look like they were 'mine'.
>
> Bugzilla has a bad habit of adding people to tickets when you comment on it.

Honestly, that seems like a _good_ habit to me, since if you commented on it, presumably, you care about it. I'd miss a lot more if I had to remember to manually subscribe to each bug that I commented on. But either way, it's a moot issue with regards to D stuff going forward, since we'll be using github instead, for better or worse, and we'll get whatever behavior they have. I _think_ that they also subscribe you to any issues that you comment on, but I haven't reported or commented on issues much on github previously, so I don't remember for sure. I guess that I'll have to watch out for that.

> So you would have interacted with each of the tickets to get the email.
>
> Not everyone got the same number as you.
>
> I only got ~12.

I also got quite a few e-mails, and I likely would have gotten _way_ more if the migration bot were commenting on issues that had been closed as well. But I'm also perfectly fine with getting e-mails for all of the various issues that I've created or commented on. It helps me keep track of things.

- Jonathan M Davis

On Sunday, December 1, 2024 12:26:25 PM MST Robert Schadek via Digitalmars-d- announce wrote:
> Earlier today I migrated the phobos' bugzilla issues from bugzilla to github https://github.com/dlang/phobos/issues
>
> Next I'll move druntime and dmd (this year).
>
> Sorry to taking so long.

Just an FYI for anyone trying to adjust their e-mail filters so that PRs and issues from github go into separate folders...

While the project itself can be filtered on by the subject (e.g. e-mails from github related to Phobos start with "[dlang/phobos]"), or by the "To" header (e.g. "dlang/phobos <phobos@noreply.github.com>"), there isn't any such distinction between types of e-mails for a given project. After some poking around, from what I can tell, it's the "Message-ID" header that needs to be filtered on to get this information. For instance, one of the recent e-mails I received for an issue for Phobos has

Message-ID: <dlang/phobos/issues/10346/2510910870@github.com>

whereas a recent e-mail about a PR has

Message-ID: <dlang/phobos/pull/10570/c2510278253@github.com>

Depending on your e-mail client, this could be a bit of a pain to filter on (e.g. in mine, I have to search for "Message-ID: <dlang/phobos/issues" within the entire message, since it doesn't let me filter on the "Message-ID" header specifically), so this is kind of unfortunate, but at least with how github is currently set up, it's the only way that I could find. And since it took a bit of investigation to figure it out, I figured that I'd pass the information along so that other folks wouldn't have to go to that same effort.

- Jonathan M Davis

You want hundreds of copies of a message that all say: "this issue was
migrated to github"? Just in case you missed that the first time?
It's an automated message, there's no information being delivered here...


On Tue, 3 Dec 2024 at 12:58, Jonathan M Davis via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote:

> On Monday, December 2, 2024 5:39:11 PM MST Manu via Digitalmars-d-announce wrote:
> > I received several hundred emails, and then had to spend ages deleting
> them
> > all... I couldn't select-all because they spanned like 10 pages, and I
> had
> > to de-select the real emails interleaved among them.
> > I'm gonna go way out there on the limb and say, I am completely confident
> > that nobody wants that.
>
> Personally, I most definitely want that. I keep all such e-mails, and I
> have
> e-mail filters which put them in the correct folders. No manual processing
> is required, and I have all of those e-mails to search through when I need
> to. I can totally understand that it's annoying to have to manually go
> through hundreds of e-mails, but e-mail programs provide tools for dealing
> with that sort of thing, and it's not exactly new that bugzilla e-mails
> about any comments or changes to bug reports that you're subscribed to.
> It's
> just that on this particular occasion, a whole bunch of issues got
> commented
> on at once because of the migration. Either way, it's a one time thing (or
> I
> guess, a two time thing, since the dmd/druntime issue still need to be
> moved), and that's the end of it.
>
> For me at least, the annoying part about the messages is that I now have to
> rework my filters to deal with github sending me e-mails about issues for
> these repos, and I need to separate those out from e-mails about PRs,
> whereas before, I could just put all of the e-mails for each repo in a
> folder for that repo and mostly be able to rely on them all being
> PR-related
> e-mails. But that's just life when we change the service we're using for
> bug
> reports.
>
> - Jonathan M Davis
>
>
>
>

On Tuesday, December 3, 2024 2:23:32 AM MST Manu via Digitalmars-d-announce wrote:
> You want hundreds of copies of a message that all say: "this issue was
> migrated to github"? Just in case you missed that the first time?
> It's an automated message, there's no information being delivered here...

It indicates that that particular issue was open at the time that the migration happened, and so it's part of the migration. It also gives the link to the corresponding issue on github, making it easier to find.

- Jonathan M Davis

On Monday, December 2, 2024 5:42:41 PM MST Manu via Digitalmars-d-announce wrote:
> I had assumed everybody got the same flood of emails that I got... they did not look like they were 'mine'.

Actually, looking at my e-mails again, it _is_ possible that you got e-mails for every issue that was migrated. It depends on what you signed up for. Bugzilla should only be sending you e-mails for issues that you created, commented on, or otherwise subscribed to. However, there's also a mailing list that sends e-mails for everything on dlang's bugzilla. Personally, I have both with them set up with them going into separate folders. So, I can see all of the bug-related stuff as it comes in (though I often end up ignoring it), and I can see which issues are actually the ones that I'm associated with in some fashion, since those end up in their own folder.

So, if you're signed up for the digitalmars-d-bugs@puremagic.com mailing list, then you'd be getting an e-mail for every issue that was migrated. However, if you're not, then presumably, you created or commented on over a thousand issues for Phobos that have yet to be resolved, since you got over a thousand e-mails from the Phobos issue migration.

- Jonathan M Davis

On Tue, 3 Dec 2024 at 20:41, Dennis via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote:

> On Tuesday, 3 December 2024 at 00:42:41 UTC, Manu wrote:
> > I had assumed everybody got the same flood of emails that I got... they did not look like they were 'mine'.
>
> Are you talking about emails from bugzilla, or GitHub? I notice you are watching Phobos on GitHub like me: https://github.com/dlang/phobos/watchers?page=2
>
> I did get about 450 emails from GitHub, but in Gmail a search for 'dlangBugzillaToGithub' let me delete them all.
>

Yeah, sure; I deleted them. I just think that emailing hundreds or
thousands of emails to potentially hundreds or thousands of people is
bad-form... it just feels like a "yeah, you just don't do that" kind of
thing to me. YMMV.
I just thought it was worth a mention, since there was likely to be more...
now I'm just astonished this is somehow controversial.

🤷