Re: [python-committers] Comments on moving issues to GitHub
Le 19/05/2018 à 02:10, Victor Stinner a écrit : > Hi, > > I failed to get the microphone after Mariatta's secret talk about > moving Python issues from bugs.python.org (Roundup) to GitHub. A "secret talk"? What is that? > I don't have a strong opinion about moving issues to GitHub. If that's on the table, it seems to me that categorization, sorting and filtering on GitHub issues is rather poor, while the basic UI experience (editing messages, etc.) is better. Also, I think customization (e.g. of the default view) is basically inexistent. Regards Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Comments on moving issues to GitHub
On Sun, May 20, 2018 at 10:56:21AM +0200, Antoine Pitrou wrote: > If that's on the table, it seems to me that categorization, sorting and > filtering on GitHub issues is rather poor, while the basic UI experience > (editing messages, etc.) is better. Also, I think customization (e.g. > of the default view) is basically inexistent. Also search via Google "site:bugs.python.org " usually gives quite nice results, while the same for GitHub issues usually does not work at all (far too many unrelated results). Then there's the original promise of the GitHub migration that in the case of GH bankruptcy or a sudden lockdown the tracker would still be available. Stefan Krah ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Comments on moving issues to GitHub
On Sun, May 20, 2018, 03:18 Antoine Pitrou wrote: > > Le 19/05/2018 à 02:10, Victor Stinner a écrit : > > Hi, > > > > I failed to get the microphone after Mariatta's secret talk about > > moving Python issues from bugs.python.org (Roundup) to GitHub. > > A "secret talk"? What is that? > She gave a talk at the language summit to discuss what people thought of the idea, and she had some fun making the topic a surprise so she could see people's reactions. I don't think there's any secret beyond that. IIRC, the general reaction was that it was definitely worth exploring, but that it would be a lot of work and require solutions to a lot of problems to make sure people's workflows weren't too impacted, so we'd need a much more detailed proposal before any decision could be made. -n ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Comments on moving issues to GitHub
On May 20, 2018, at 10:19, Nathaniel Smith wrote: > > IIRC, the general reaction was that it was definitely worth exploring, but > that it would be a lot of work and require solutions to a lot of problems to > make sure people's workflows weren't too impacted, so we'd need a much more > detailed proposal before any decision could be made. Note too that Bryan Clark from GitHub, who I believe is a product manager there, was at the packaging mini-summit. If/when we have a specific set of asks for the migration, we can reach out to him and see how they can help. For example, I specifically asked about my favorite GitLab feature “commit when CI passes” and it sounded like they were working on that. -Barry signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Comments on moving issues to GitHub
On Sun, 20 May 2018 at 10:43 Barry Warsaw wrote: > On May 20, 2018, at 10:19, Nathaniel Smith wrote: > > > > IIRC, the general reaction was that it was definitely worth exploring, > but that it would be a lot of work and require solutions to a lot of > problems to make sure people's workflows weren't too impacted, so we'd need > a much more detailed proposal before any decision could be made. > > Note too that Bryan Clark from GitHub, who I believe is a product manager > there, was at the packaging mini-summit. If/when we have a specific set of > asks for the migration, we can reach out to him and see how they can help. > For example, I specifically asked about my favorite GitLab feature “commit > when CI passes” and it sounded like they were working on that. > There was also general consensus that the state of maintenance for bpo is subpar due to lack of staffing and that more people will need to come forward to help maintain it if we decide to not transition to another issue tracker like GitHub or GitLab. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] 3.7.0rc1 deadline extended two days to 2018-05-23 AOE [Re: FINAL WEEK FOR 3.7.0 CHANGES!]
We are going to extend for 48 hours the deadline for 3.7.0rc1, that is, until 2018-05-23 23:59 AOE. While we have made tremendous progress towards the release candidate over the past week especially with the huge efforts at the PyCon US Sprints, we still have some important issues to resolve. A stumbling block has been the increased instability in the test suite, primarily in test_asyncio, which has caused delays in merging PRs due to intermittent failures in CI test runs and which has caused widespread buildbot failures. Another factor is that this weekend and Monday are public holidays in many countries, something I did not take into account when drawing up the schedule. (Note that next weekend is a major public holiday in the USA.) So let's plan on using the extra two days to work through the remaining release blockers. Thanks again! --Ned On May 15, 2018, at 07:51, Ned Deily wrote: > This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your > feature fixes, bug fixes, and documentation updates in before > 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days > from now. We will then tag and produce the 3.7.0 release candidate. > Our goal continues been to be to have no changes between the release > candidate and final; AFTER NEXT WEEK'S RC1, CHANGES APPLIED TO THE 3.7 > BRANCH WILL BE RELEASED IN 3.7.1. Please double-check that there are > no critical problems outstanding and that documentation for new > features in 3.7 is complete (including NEWS and What's New items), and > that 3.7 is getting exposure and tested with our various platorms and > third-party distributions and applications. Those of us who are > participating in the development sprints at PyCon US 2018 here in > Cleveland can feel the excitement building as we work through the > remaining issues, including completing the "What's New in 3.7" > document and final feature documentation. (We wish you could all be > here.) > > As noted before, the ABI for 3.7.0 was frozen as of 3.7.0b3. You > should now be treating the 3.7 branch as if it were already released > and in maintenance mode. That means you should only push the kinds of > changes that are appropriate for a maintenance release: > non-ABI-changing bug and feature fixes and documentation updates. If > you find a problem that requires an ABI-altering or other significant > user-facing change (for example, something likely to introduce an > incompatibility with existing users' code or require rebuilding of > user extension modules), please make sure to set the b.p.o issue to > "release blocker" priority and describe there why you feel the change > is necessary. If you are reviewing PRs for 3.7 (and please do!), be on > the lookout for and flag potential incompatibilities (we've all made > them). > > Thanks again for all of your hard work towards making 3.7.0 yet > another great release - coming to a website near you on 06-15! > > Release Managerly Yours, > --Ned > > https://www.python.org/dev/peps/pep-0537/ -- Ned Deily [email protected] -- [] ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
