[Python-Dev] Workflow proposal (original) (raw)
Jesus Cea jcea at jcea.es
Wed Mar 23 14:05:19 CET 2011
- Previous message: [Python-Dev] Workflow proposal
- Next message: [Python-Dev] "Meet the Team" on Python Insider
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22/03/11 18:38, Jesus Cea wrote:
Most of our problems are related to trying to keep a lineal history, and races with pull-patch-commit-push cycle. I propose the following workflow.
The points of my proposal are:
The hg.python.org repository has the branches ALWAYS merged. This must be enforced by the push hooks.
We need a way to test code in the buildbots, without committing the patch to the "real" repository.
How to do "2" and how to solve the push race in "1", are not the point :-). I do an approach suggestion for both, just for the sake of completeness, for I want to stress that the my actual contribution is "1" and "2" :).
Jesus Cea Avion // /// /// jcea at jcea.es - http://www.jcea.es/ // // // // // jabber / xmpp:jcea at jabber.org // // ///// . // // // // // "Things are not so easy" // // // // // // "My name is Dump, Core Dump" /// //_/ // // "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTYnwD5lgi5GaxT1NAQKxVAP7BelEjoSz91zCQodvmdP8E03pP+W6xJhR DAwMcerrqGfV/XP45HvMk8kjwHuGQvA4jmvi+M/8QWnpJ3g3YoTR7ADHzzpF1ngq Fx0D3bAxwPFJQhiEMbFOrH3v5+9vbo5T26pUHUlDbF+/rcEY82m7GWAv4QqmceQ8 nbJ3PETIYf8= =m9qH -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] Workflow proposal
- Next message: [Python-Dev] "Meet the Team" on Python Insider
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]