On Nov 25, 9:50 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 25, 2008 at 9:47 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Nov 25, 9:42 pm, "Minh Nguyen" <[EMAIL PROTECTED]> wrote:
> >> On Wed, Nov 26, 2008 at 4:29 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> >> > On Tue, Nov 25, 2008 at 5:10 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> >> >> Hello folks,
>
> >> >> athttp://trac.sagemath.org/sage_trac/ticket/4567youcan find my
> >> >> attempt to finally catch up with the release notes of the last three
> >> >> Sage releases. I know, I know, I am rather late, but things keep
> >> >> getting in the way. What is now needed to push the official button on
> >> >> 3.2 is a listing of the main new features. This is also required for
> >> >> 3.1.3 - 3.1.4 was a bug fix release so there is little left to do.
>
> >> > Michael has expressed a strong interest in somebody else taking
> >> > over the role for a while of "official release notes" maker. Is anybody
> >> > interested. This doesn't l33t coding skills, but is an extremely
> >> > important
> >> > task, and could be an excellent way for you (yes you) to volunteer
> >> > and help make Sage better. This isn't something you would have to do
> >> > forever -- most things with Sage are like a relay race.
>
> >> Yeah, I'm willing to help out with making a release note that is part
> >> of each Sage distro, although I'm stilling learning my way through
> >> Sage itself. Please remind me of the process I need to follow. For
> >> example, if I have a partial release note for an upcoming release (or
> >> a current release), which server do I upload that note to? etc.
>
> > What I primarily need is someone to take care of the Sage Release Tour
> > bit of the release notes - everything else I do while I merge patches.
> > Then in the end it would be useful if someone does spell and fact
> > check the end result. Right now for example there is draft2 of the
> > 3.1.3, 3.1.4 and 3.2 release notes at #4567 and I am sure they could
> > use some checking.
>
> Cool -- so here Minh can (1) proofread whatever you make, and (2) make sure
> that you didn't miss something (i.e., look for differences between what
> trac said happened and what you list in the notes).
Yes.
> > 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.
Having excellent release notes is very important IMHO especially for
people who do not live in trac and just get an email every 2 to 4
weeks that there is a new Sage release. And that is why I made the
release notes a trac ticket so I get credit for them because often I
spend more time on release notes than fixing individual bugs :)
> -- William
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
