On Feb 23, 2:07 am, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi Paul,
>
> On Mon, Feb 23, 2009 at 9:58 AM, Paul Zimmermann
>
> <paul.zimmerm...@loria.fr> wrote:
>
> >> And here's a nicely formatted version of the release tour:
> >>http://mvngu.wordpress.com/2009/02/23/sage-33-released
>
> > this is very nice! I wonder how much time it took you to write this page.
Indeed, I am extremely happy with the results :). The release tour is
something that due to other things to do has always been something
where I wanted to improve what I did pre-Minh, but never got around to
it. Given that this is very much the first stop for people to check
what happened in the release it cannot be overemphasized how important
this page is. And it will become ever more important as we gather more
users that do not read support or development lists.
> I had been working on the releae tour of 3.3 at
>
> http://wiki.sagemath.org/sage-3.3
>
> since the first few tickets were closed in that milestone. As more
> tickets were closed, I read/skimmed through them for interesting
> features and noted down those features in the above wiki. So the
> release tour was pretty much a work in progress.
Note that everybody is welcome to help Minh out with this and Martin
Albrecht did do so for the Sage 3.3 release tour as seen in
http://wiki.sagemath.org/sage-3.3?action=info
I think that any "big feature" or important fix should automatically
be accomplished by a snipped in wiki text to be added to the release
tour.
There are some important things missing from the list of changes, i.e.
fixes to the S-integral point counting code to name one, but given 385
tickets closed against 3.3 this can hardly be blamed on Minh :). What
I will try to do in the future is to create stub entires in the
current Sage release tour for tickets I consider important, so
hopefully this will be less likely to happen.
> This afternoon
> (Australian time) I took the wiki page as base and fleshed out my blog
> post. The beautiful post that you saw took me an afternoon to format.
Yep, this should make a great impact since it is too hard for many
people not too tightly involved with the development process to
distill the changes from the ticket list and figure out what is
important and what not. Many of the ticket summaries are also hard to
understand without insider knowledge.
And in general: the more pretty pictures we have the better it is :)
> --
> Regards
> Minh Van Nguyen
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
