On 01/10, Brett Cannon wrote: > For those of you who have not heard, I made the decision a little over a > week ago to move Python's development from our home-grown workflow to one > hosted on GitHub (mainly for code hosting and code review; we're keeping > bugs.python.org for our issue tracker). The hope is that this will let core > developers work through patches faster so that we have a better turn-around > time while being at least as good as our current workflow for external > contributors (but I will be shocked if it isn't better). There are also > people involved with the migration who plan to put in the effort to make > sure external contributors can still submit patches without ever > interacting with GitHub. > > If you want to help with the transition, then feel free to join the > core-workflow mailing list where all the discussions on the details of the > migration are occurring (including the PEP I'm starting to write to outline > the steps we will be taking): > https://mail.python.org/mailman/listinfo/core-workflow > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/stephane%40wirtel.be \o/ Already on core-workflow. -- Stéphane Wirtel - http://wirtel.be - @matrixise
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4