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. ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel