github workflow - matplotlib-devel - Matplotlib
github workflow Development matplotlib-devel _John_Hunter September 1, 2011, 2:54am 1 github workflow: this seems to present a different workflow than that espoused in gitwash used by mpl and other projects http://scottchacon.com/2011/08/31/github-flow.html I like the idea of lots of feature branches off upstream/master and master always being deployable (nightly builds?). What is the advantage of core devs working in their own forks, as we currently do, over working on feature branches off of https://github.com/matplotlib/matplotlib ?
Seems like a lighter-weight approach that works, and it would probably make it easier for users to follow mpl development by tracking the mpl repo and all the branches off of it, rather than having to pull in the various dev's forked branches. _Matthew_Brett September 1, 2011, 3:16am 2 Yo, github workflow: this seems to present a different workflow than that espoused in gitwash used by mpl and other projects http://scottchacon.com/2011/08/31/github-flow.html I like the idea of lots of feature branches off upstream/master and master always being deployable (nightly builds?).
What is the advantage of core devs working in their own forks, as we currently do, over working on feature branches off of GitHub - matplotlib/matplotlib: matplotlib: plotting with Python ? Seems like a lighter-weight approach that works, and it would probably make it easier for users to follow mpl development by tracking the mpl repo and all the branches off of it, rather than having to pull in the various dev's forked branches.
The issue being - why not have all the development branches in the same main repo? Because: a) Everyone needs write access to the main repo b) It's much less tempting to start experimental and highly unstable branches c) You can get a very similar effect by adding remotes to your own repo. d) It only very slightly simplifies an unusual case (what's developer X working on today?). Less tempting ··· On Wed, Aug 31, 2011 at 7:54 PM, John Hunter < [email protected] ...> wrote: ------------------ Just as a minor example, here's my nipy branch list: Lots of crap in there; I just made a branch with a single extra commit that I may well throw away, the branch I'm currently working on: - I am constantly rebasing and reorganizing while I try to work out what I'm doing.
I'd think much harder about that if I thought other people were expecting to pull down all my stuff. Thinking harder = slower coding (for me at least :)) Similar effect ---------------- - I'd like to see what Gael and Jonathan Taylor are up to from time to time: Once: git clone [email protected] ...:matthew-brett/nipy.git # origin remote git remote add gael git://github.com/GaelVaroquaux/nipy.git git remote add jonathan git://github.com/jtaylor/nipy.git From time to time: git fetch --all - same effect, and it allows me to chose who I'm following.
But actually, I very rarely do that in the abstract, I look when they tell me to look at something, and I'm pretty sure it's the same for them and my stuff. See you, Matthew Benjamin_Root1 September 1, 2011, 3:34am 3 I agree with Matthew here, but I could see a possible hybrid approach. Let’s say we were a more organized group (I will wait for the laughter to die down…), then one could imagine having branches with names of approved milestones/goals/planned features for the next release.
The names would convey the features actively being worked on, and provide a focus for us. When a feature is finished, we then merge into master. If a feature is not ready for prime-time, then we can just hold it off. Just a thought, Ben Root ··· On Wed, Aug 31, 2011 at 10:16 PM, Matthew Brett <matthew.brett@…149…> wrote: Yo, On Wed, Aug 31, 2011 at 7:54 PM, John Hunter <jdh2358@…149…> wrote: github workflow: this seems to present a different workflow than that espoused in gitwash used by mpl and other projects http://scottchacon.com/2011/08/31/github-flow.html I like the idea of lots of feature branches off upstream/master and master always being deployable (nightly builds?).
What is the advantage of core devs working in their own forks, as we currently do, over working on feature branches off of https://github.com/matplotlib/matplotlib ? Seems like a lighter-weight approach that works, and it would probably make it easier for users to follow mpl development by tracking the mpl repo and all the branches off of it, rather than having to pull in the various dev’s forked branches. The issue being - why not have all the development branches in the same main repo?
Because: a) Everyone needs write access to the main repo b) It’s much less tempting to start experimental and highly unstable branches c) You can get a very similar effect by adding remotes to your own repo. d) It only very slightly simplifies an unusual case (what’s developer X working on today?). Less tempting Just as a minor example, here’s my nipy branch list: https://github.com/matthew-brett/nipy/branches Lots of crap in there; I just made a branch with a single extra commit that I may well throw away, the branch I’m currently working on: https://github.com/matthew-brett/nipy/tree/fmristat-test-refactor I am constantly rebasing and reorganizing while I try to work out what I’m doing.
I’d think much harder about that if I thought other people were expecting to pull down all my stuff. Thinking harder = slower coding (for me at least :)) Similar effect I’d like to see what Gael and Jonathan Taylor are up to from time to time: Once: git clone git@…679…:matthew-brett/nipy.git # origin remote git remote add gael git:// github.com/GaelVaroquaux/nipy.git git remote add jonathan git:// github.com/jtaylor/nipy.git From time to time: git fetch --all same effect, and it allows me to chose who I’m following.
But actually, I very rarely do that in the abstract, I look when they tell me to look at something, and I’m pretty sure it’s the same for them and my stuff. See you, Matthew _John_Hunter September 1, 2011, 3:37am 4 Yo, github workflow: this seems to present a different workflow than that espoused in gitwash used by mpl and other projects http://scottchacon.com/2011/08/31/github-flow.html I like the idea of lots of feature branches off upstream/master and master always being deployable (nightly builds?).
What is the advantage of core devs working in their own forks, as we currently do, over working on feature branches off of GitHub - matplotlib/matplotlib: matplotlib: plotting with Python ? Seems like a lighter-weight approach that works, and it would probably make it easier for users to follow mpl development by tracking the mpl repo and all the branches off of it, rather than having to pull in the various dev's forked branches.
The issue being - why not have all the development branches in the same main repo? Because: a) Everyone needs write access to the main repo I'm thinking about core devs here -- they all have write access to the main repo. Users and non core devs can continue with the fork approach. b) It's much less tempting to start experimental and highly unstable branches This can still be done in forks. And experimental and unstable branches are a minor threat -- they may increase the signal-to-noise, but dead branches can be pruned and users and devs can probably get a pretty good feel for which are active by looking at the "last update" time on the branch list. c) You can get a very similar effect by adding remotes to your own repo.
Yes, I do this and I'm sure other mpl developers do to, but you need to know who to follow, which is harder for the casual developer or user. By having the core devs develop in feature branches off of upstream, it makes it easier for users and other developers to see what all the other cores devs are up to w/o having to specify who to track. They track the main repo, they see the main work of the core devs as they come and go. d) It only very slightly simplifies an unusual case (what's developer X working
The rest of this page is on the live site.