Te next question arises -- do we gather information about the number of users based on this? I'm scared -- I don't want SAGE to be called "evil spyware!"
---------- Forwarded message ---------- From: Arthur Gaer <[EMAIL PROTECTED]> Date: May 18, 2007 12:01 PM Subject: Re: [sage-devel] Re: automatic sage upgrade notification? To: William Stein <[EMAIL PROTECTED]> William, I go off to a meeting and, like, you and your cohort solve the problem! :) Yeah, I think this could be a really good way to go, including the suggestion of "latest stable version..." in the banner. And, btw, this would also be a way of getting a rough idea of number of current SAGE users--very rough (behind NATing firewalls and stuff), but still, counting every unique IP address query every week/ month or so. Arthur On May 18, 2007, at 2:37 PM, William Stein wrote: > ---------- Forwarded message ---------- > From: Robert Bradshaw <[EMAIL PROTECTED]> > Date: May 18, 2007 11:29 AM > Subject: [sage-devel] Re: automatic sage upgrade notification? > To: sage-devel@googlegroups.com > > > > On May 18, 2007, at 10:01 AM, Nick Alexander wrote: > >> One way to make notifications less obtrusive is to make them >> omnipresent. That is, the banner could always read >> >> --------------------------------------------------------------------- >> - >> | SAGE Version 2.5.alpha2, Release Date: 2007-05-02 >> | Latest version is 2.5.alpha3, type upgrade() to upgrade. >> | Type notebook() for the GUI, and license() for >> information. | >> --------------------------------------------------------------------- >> - >> >> While we're at it, maybe the banner should also tell you if you're >> running a vanilla sage or a hacked sage and maybe what the last hg >> tag >> was. > > I like this idea. It would be nice if you could get this information > from the notebook too--and if (somewhere unobtrusively) it had the > name of the branch you were working on (assuming it's not main, this > is something I've actually wanted for a while). > > I might also have something like "Latest stable version...", not > alphas, etc. Perhaps only major releases, (or x.x.1 'cause those > often catch the last couple bugs if any, but don't introduce new > ones--it might even be worth having a "bug fix" branch which is the > latest stable release + bug fixes only if we're thinking of automatic > upgrade prompts). > > - Robert > > > > > > -- > William Stein > Associate Professor of Mathematics > University of Washington > http://www.williamstein.org -- William Stein Associate Professor of Mathematics University of Washington http://www.williamstein.org --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
