On 06/15/2011 12:13 PM, Darren Dale wrote: > On Wed, Jun 15, 2011 at 10:06 AM, John Hunter<jdh2...@gmail.com> wrote: >> On Wed, Jun 15, 2011 at 9:02 AM, Darren Dale<dsdal...@gmail.com> wrote: >> >>> I suggest we make a 1.1.x branch from the current state of master, and >>> consider it as a placeholder for now. Then we bump the version number >>> in the py3 repo to *2.0*, merge py3/master back into mpl/master, and >>> delete the py3 repo. The reason for bumping to v2.0 is simply to draw >>> everyone's attention to the fact the next release will be the first to >>> drop support for<=python-2.5. Once folks start working with the >>> master (2.0) branch, if we have any complaints that a version 1.1 >>> release was needed after all, we can cut it from the 1.1.x placeholder >>> branch. >> This works for me -- I obviously dropped the ball pushing for a 1.1 >> release, but this will be a good impetus. Should we give people a >> couple of days to close any open tickets they want or push any last >> minute changes in that we want before making the 1.1 release branch? >> Once we branch, I suggest only release critical bug fixes go in as we >> discussed last. > Each pull request gets assigned to an issue.
How do I apply labels to an issue with an associated pull request? I see how to do it for free-standing issues, but not the pull request ones. > I just added two labels > in the github issue tracker: wishlist and ongoing. So, to be clear, "wishlist" means "would be nice to have, but no real target date", and "ongoing" means someone is working on it? > I also created two > milestones: v1.1.0 and v2.0.0. Could the devs please look through the > issues and assign each one to either one of the milestones or apply > the wishlist label? I could try to merge the issues from sourceforge > as well, though that may take some time. It would be nice to merge those in -- wasn't there some tools other projects were using to import them en masse? If we do so, I would also suggest (somewhat controversially) that we deleted everything before some arbitrary cut off date. There are a lot of really old, and most likely obsolete bugs in there, and we should probably just declare bankruptcy on them. Cheers, Mike -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
