On Fri, Jun 3, 2011 at 9:04 AM, Benjamin Root <ben.r...@ou.edu> wrote:
> > > Plus, with regards to timing. Do we want to release before or after the > upcoming SciPy conference in July? Depending on who will be there > (unfortunately, I won't be), we might want to wait for after that conference > to take advantage of any activity then. > > I don't feel the need to wait -- things move slowly enought that we might get one release out in the next couple of weeks and one bugfix release 2-4 weeks after that and that will dovetail with scipy conference. Also, my June is a lot better than my July as I will be traveling in July for the first couple of weeks. > Also, I know I have repeatedly stated that I won't be a release manager, > but I am going to put together a wish-list of mine for what I would like to > see for the next release. Maybe with that as a base, we can come up with a > final set of goals for v1.1.0 and determine how much time it would take to > get there? > This might be a better idea for a 1.2 release, since this sounds like it will take a while. There has been a lot of progress in the trunk since 1.0.1 and with the release-early-release-often philosophy I'd rather get something out there and then if we want to do something more formalized for the next iteration we will have plenty of time for it. I would shoot for people to get their changes in for a 1.1 release by early next week, branch and cut a release candidate, test for a week and put in bug fixes, cut a second release candidate a week later. If people would like more time for a formal process and bug closing extravaganza, I'm fine with that too. JDH
------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
