Hi folks, Mike Hansen has written a script [1] to automatically generate a release note for a Sage milestone. I have updated Mike's script with the following changes:
* re-order code to separate helper functions from the main part of the script, with some general clean up * allow one point of entry into each helper function * a variable "maxtickets" to configure the number of tickets to display on the trac report. The number of tickets to display on a trac report is by default 100. Some milestones close more than 100 tickets. By default, the variable "maxtickets" is set to 1000 tickets. * use urllib2 instead of urllib * document the helper functions get_sections(), print_contributors(), and print_section() * sort tickets in non-decreasing order when printing closed tickets The updated script [2] with the above changes are available from my boxen.math directory. The release management wiki page [3] has been updated to provide a link to Mike's script. See especially the section "Release checklist" on that wiki page. [1] http://groups.google.com/group/sage-release/msg/18c0a2af062bcc5a [2] http://boxen.math.washington.edu/home/mvngu/apps/release-notes/ [3] http://wiki.sagemath.org/devel/ReleaseManagement -- Regards Minh Van Nguyen
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
