The 1.3.0 release candidate tagging is scheduled for this coming Monday, May 27. Unfortunately, due to an oversight on my part, I forgot that is a holiday, so I'm going to postpone it one day to Tuesday, May 28. I will be hoping to tag the release by 23:00 UTC that day.
I think we're in really good shape for this release, given all of the great work solving and triaging bugs that's been going on since the feature freeze. I think all of the blocker bugs (except possibly #2061) are really close to being resolved. There are a number of issues tagged for 1.3.x that may unfortunately need to get punted, but not a very large number. Question: Should I create a 1.3.x branch now? The upside of doing that is that development of post-1.3.x things can continue on master until Tuesday, of course, and I think the pool of 1.3.x things is small enough for that to make sense. The downside, of course, is that any existing pull requests against master will have to be manually merged to 1.3.x. That shouldn't be a big deal, though, because we don't have too many of them left and I can just pull the PR logs when I'm back at the office on Tuesday to find out which ones need to be merged. Any objections to creating the branch now? Mike ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
