Hi, On Tue, Sep 6, 2011 at 8:38 AM, Michael Droettboom <md...@stsci.edu> 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, it isn't very discoverable that a solution may already > exist, and the user can waste time wondering if it's a bug or user error > etc. Perhaps a compromise between these two approaches would be to have > a wiki page which is a directory of any branches that developers > consider interesting and want to point people toward? Maybe that's just > creating busy work, of course.
Maybe the summary is that putting the branches in the main repo labels those branches somehow. You're suggesting the label means 'you might consider merging these to see if they fix your bug'. John is suggesting the label means 'here are the main threads of development going on'. Of course you have another virtual label which is 'branch in pull request state'. Maybe, as Fernando says, that's the best label to use for a branch that the user might consider merging? See you, Matthew ------------------------------------------------------------------------------ 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
