I agree with you, Ned. Mariatta, I'm happy to work on an initial pass at the devguide in my fork.
On Fri, Jun 28, 2019 at 10:52 AM Ned Deily <[email protected]> wrote: > > On Jun 28, 2019, at 12:56, Mariatta <[email protected]> wrote: > > Some of the items brought up during the language summit: > > [...] > > - we should be updating devguide ahead of the actual migration, so core > developers and release managers have time to review and learn the new > workflow. (suggested by Ned Deily) > > Actually, my suggestion was (and remains :) ) that a modified devguide > branch should be created *first* as part of the migration design process, > not later during implementation. It needs to happen anyway but it would be > much more effective, I think, to have it available up front to help catch > any holes during the design and review. > > P.S. Thanks for doing this, Marietta! > > -- > Ned Deily > [email protected] -- [] > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/JPWPWUUYDRWNWALTVT4VIT4L6WMBNIRJ/ > -- *Carol Willing* Willing Consulting <https://willingconsulting.com> *Signature strengths* *Empathy - Relator - Ideation - Strategic - Learner*
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/YPUM4W7C7SBLJQQVVIM7CKPDBSQN7QOP/