On Wed, Jul 14, 2010 at 3:41 PM, Jonathan <gu...@uwosh.edu> wrote: > I'd like to get wider distribution of the new interface for Jmol. I'm > sure it is not perfect, but I'm getting no feedback with it as an > optional .spkg. I'm pretty sure it works as well as what is in Sage > now, so although it needs input and work,
What work does it need? > I would like to argue for > including it, so that we can start getting feedback. > > Jonathan > > On Jul 13, 6:49 pm, William Stein <wst...@gmail.com> wrote: >> Hi Sage Developers, >> >> I'm setting the Sage-5.0 target date for August 31, 2010 >> (seehttp://trac.sagemath.org/sage_trac/milestone/sage-5.0). The goals >> are: >> >> 1. Windows port via >> Cygwin:http://trac.sagemath.org/sage_trac/wiki/CygwinPort >> 2. Upgrade PARI to svn: #9343 >> 3. Upgrade MPIR to version 2.x: #8664 >> 4. Raise the coverage score to 90% >> 5. (Done) Sparc Solaris 10 >> >> What follows is a brief discussion of the status of each of these. >> >> 1. Windows port via >> Cygwin:http://trac.sagemath.org/sage_trac/wiki/CygwinPort >> >> There is still some work to do on this. See the 13 tickets I opened at >> >> http://trac.sagemath.org/sage_trac/wiki/CygwinPort >> >> So far, Mike Hansen has done an amazing job on this (I've helped some >> too). We could really, really use help here, especially because >> this work can go on independently of other things. This document >> explains a lot about cygwin:http://cygwin.com/cygwin-ug-net/ >> >> 2. Upgrade PARI to svn: #9343 >> >> Robert Bradshaw, John Cremona and I did a huge chunk of this two weeks >> ago, and John also did a bunch more yesterday. What remains is just >> resolving a few doctest failures, some of which might be subtle. >> >> 3. Upgrade MPIR to version 2.x: #8664 >> >> Nobody has done anything on this for two months. Anybody could work >> on this. It's very easy -- just make an spkg, then test the sage >> build and report issues. Pretty straightforward for almost anybody to >> do. >> >> 4. Raise the coverage score to 90% >> >> If you delete the devel/sage/sage/server directory, then Sage-4.5.rc0 >> has this coverage score: >> >> Overall weighted coverage score: 84.6% >> >> So we have barely even budged in a while. That said, I suspect there >> are a lot of doctest patches that just need review or have positive >> reviewed, but need to get merged into sage-4.5.rc0. >> >> 5. (Done) Sparc Solaris 10 >> >> This is done. >> >> ---- >> >> (Note: the above are the Sage-5.0 goals. This is not negotiable. If >> you disagree with them, send email to sage-flame, not this list.) >> >> -- William > > -- > 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 > -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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