Hello folks, 2.8.13 is about to be released, but I would like to make a couple remarks of things I think we can do to have a better release next time:
* Mandatory patch review is good, but instead of waiting for the actual merge cycle it would be better if the autor[s] of a patch/ patches would ask for review right after posting a patch/patches. That way there isn't a mad rush for review requests toward the end of the merge cycle * Please doctest the whole testsuite, especially if you touch files like parent.pyx, coerce.pyx because of potential side effects all over the place * Doctesting is a good idea, especially if you upgraded a spkg to a major new version. It would also be a good thing if you mentioned the platform you build tested on. As I experienced first hand there can be quite a difference in between OSX 10.5 in x86 vs. OSX 10.4 on PPC. * We need better human readable change logs, pointing people to track is convenient. What I would like is something similar to the Magma release docs. For example if you implement and/or update something write 2 or 3 couple lines what you did. Attach those as comment to the trac ticket and I will stick all of them into the release notes. Another idea is to do this directly in the wiki. * we need a release text template. Ted did mention that he wanted to do something for Sage marketing, so there is his chance :D Obviously these ideas are great since these are mine. But feel free to come up with your own suggestions and contradict me. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
