Hi Larry!
The steering council brought this thread (that I missed) up to my attention.

On Thu, Nov 4, 2021 at 8:17 AM Larry Hastings <la...@hastings.org> wrote:
>
> I guess this is part of the migration from bpo to GitHub issues?

It is: this is one of the repos that I'm using for testing.  In
particular I'm using it for quick tests on specific issues, and it saw
some more activity during the sprints.  The issues-test-bpo repo is
updated less frequently and it's supposed to look closer to the final
version.

>  Maybe the initial work could be done in a private repo, to cut down on the 
> spurious email notifications to literally everybody subscribed to cpython?  
> Which is a lot of people.
>

The work is being done in private repos, but in order to showcase my
progress to the fellow core devs and triagers, I added these two
GitHub teams to the repos so that they could access them.  People that
don't belong to these two teams are unable to access the repository
and shouldn't have received any notification.

Unfortunately, with each import I have to destroy and recreate the
repo, and add the teams again.  I didn't realize this was sending out
notification to all core devs and triagers (and apparently not
everyone is receiving them, probably due to how they configured their
notification settings on GitHub) -- if I knew I would have been more
considerate :)

In the coming weeks, you will still receive a few more notifications
from issues-test-bpo as I reach major milestones and update the repo,
but you shouldn't see any more notification from issues-test-2 or the
other test repos.

If you would like to change your notification settings, see
https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications

If there are any other issues feel free to ping me directly, and sorry
for the noise!
--Ezio



>
> /arry
>
> _______________________________________________
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-dev@python.org/message/H5KW6GRHIF2VWOGNRH5367WB3K2GPARO/
> Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/Y4EN2IKGWIC3BNI6OCOCUPZYEAEKS7IU/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to