On Tue, Nov 25, 2008 at 10:04 PM, mabshoff <[EMAIL PROTECTED]> wrote: [...] >> > What is even more important is to do the work for the main features, >> > i.e. the Sage Release Tour in the wiki during development and not as >> > an afterthought. The best results there have always been had when the >> > patch authors did the changes themselves. It would also be great to >> > clean up the old release tours since many of them are rather >> > rudimentary. >> >> So here Minh could bug the relevant people, ask questions, etc. For >> example, Minh might directly email me and say -- Ok, explain what >> "sage -only_optional" is all about, in case trac and the relevant help >> in Sage isn't very helpful, and I'll answer, and he can proofread and >> post the result into the tour. (?) > > Exactly. It would be very nice if the release tours were consistent in > style, had plenty of examples and so on. I have always liked the Magma > release notes since they gave you a very good idea what had happened > in the 2.14.x to 2.14.x+1 release.
So, for example, can you please provide me with such a release note for a Magma version? I don't have Magma and I've never seen a release note for a Magma version. In case you're unable to provide such a note, can you please describe what you like about those notes? That is, let's take the release note for sage-3.2 as a bare minimum. What other "good" things do you want to add to newer Sage release notes? -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
