I think all of this makes perfect sense, and I'm willing to commit to at least the next 2 years. I'm glad to hear there will be some help initially, as I know I will need some spinup time/help. I'm currently out of town and away from my macbook pro, but when I get back I'll try to set up a build environment on it. In the mean time I'll work on setting up a build environment on my windows machine as practice.
I look forward to working more closely with everyone. It's about time I started giving back! Thanks, Patrick On Sat, Jan 16, 2010 at 3:40 AM, Jarrod Millman <mill...@berkeley.edu>wrote: > First I want to give David Cournapeau a big thank you for all his hard > work as release manager for the last few years. It is a lot of work > and he has done a great job managing the releases (not to mention all > the work he has done as one of the primary developers). > > I also want to thank Patrick Marsh and Ralf Gommers for stepping up to > the plate and volunteering to help with the next release. I would > like to ask you both to consider committing to managing the next few > releases. I believe managing the releases takes some skills, which > you will develop over a few releases. It will be much better for the > community and for the project if we can have some consistency over the > release process. I know David is willing to help you with at least > the first release and I am happy to help as well. > > One of the things that both David and I would really like to see is > finally moving to a time-based release. Both of us had moved in the > direction of a time-based release and I think David had more success > than I did. > > Ideally I would like to see the two of you commit to two years as > release managers. So if we move to a time-based release every 6 > months, then you would be responsible for 4 releases. > > As release managers, you will be responsible for keeping an eye of the > trunk and making sure that it stays in a healthy releasable state. It > would be great if you could work on improving the testing > infrastructure and coverage. You will need to keep a good line of > communication with the developers and keep everyone focused on the > release date. You will also need to help write the release notes and > build the binaries. > > Thanks, > Jarrod > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > -- Patrick Marsh Ph.D. Student / Graduate Research Assistant School of Meteorology / University of Oklahoma Cooperative Institute for Mesoscale Meteorological Studies National Severe Storms Laboratory http://www.patricktmarsh.com
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
