Re: [matplotlib-devel] github workflow

2011-09-06 Thread Matthew Brett
Hi, On Tue, Sep 6, 2011 at 8:38 AM, Michael Droettboom wrote: > I think most of the points being made here are valid.  However, a common > occurrence (at least for me) is for a user to struggle against a bug > that I'm currently working on in one of my branches.  Looking at the > main repository,

Re: [matplotlib-devel] github workflow

2011-09-06 Thread Fernando Perez
On Tue, Sep 6, 2011 at 9:53 AM, Michael Droettboom wrote: > It occurred to me that it's also possible to file pull requests very > early on while working on a branch.  This would make these branches that > others may care about more visible.  We would just want some convention > to say "wait -- th

Re: [matplotlib-devel] github workflow

2011-09-06 Thread Michael Droettboom
It occurred to me that it's also possible to file pull requests very early on while working on a branch. This would make these branches that others may care about more visible. We would just want some convention to say "wait -- this branch isn't done yet, don't merge". Mike On 09/06/2011 11:

Re: [matplotlib-devel] github workflow

2011-09-06 Thread Michael Droettboom
I think most of the points being made here are valid. However, a common occurrence (at least for me) is for a user to struggle against a bug that I'm currently working on in one of my branches. Looking at the main repository, it isn't very discoverable that a solution may already exist, and t

Re: [matplotlib-devel] github workflow

2011-09-01 Thread Fernando Perez
On Wed, Aug 31, 2011 at 20:16, Matthew Brett wrote: > 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 g

Re: [matplotlib-devel] github workflow

2011-08-31 Thread Matthew Brett
Hi, On Wed, Aug 31, 2011 at 8:37 PM, John Hunter wrote: > On Wed, Aug 31, 2011 at 10:16 PM, Matthew Brett > wrote: >> Yo, >> >> On Wed, Aug 31, 2011 at 7:54 PM, John Hunter wrote: >>> github workflow: this seems to present a different workflow than that >>> espoused in gitwash used by mpl and

Re: [matplotlib-devel] github workflow

2011-08-31 Thread John Hunter
On Wed, Aug 31, 2011 at 10:16 PM, Matthew Brett wrote: > Yo, > > On Wed, Aug 31, 2011 at 7:54 PM, John Hunter 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.h

Re: [matplotlib-devel] github workflow

2011-08-31 Thread Benjamin Root
On Wed, Aug 31, 2011 at 10:16 PM, Matthew Brett wrote: > Yo, > > On Wed, Aug 31, 2011 at 7:54 PM, John Hunter 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-fl

Re: [matplotlib-devel] github workflow

2011-08-31 Thread Matthew Brett
Yo, On Wed, Aug 31, 2011 at 7:54 PM, John Hunter 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/