I'd like to do some of this too, although I'm not very clear on how it would be organized -- would I look at the list of tickets, pick some, and send a sketch or draft announcement to sage-marketing? Could people who've been working on closing a big ticket send us an announcement? Would we organize a schedule for posting the feature announcements? (Maybe one or two every couple of days after the release?)
Whatever the answers are, it seems useful to look at a trac query for the tickets merged in a particular release but organized by component: http://trac.sagemath.org/query?status=closed&milestone=sage-5.13&group=component&col=id&col=summary&col=milestone&col=status&col=priority&col=author&order=priority Then I could skip to the components that I know more about our am more interested in, and click over to read the tickets. The list for 6.0 doesn't have so much in it, presumably because that release is just about switching to git, but in general the list of closed tickets merged in an upcoming release should be the right list, shouldn't it? -Niles -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
