Alex Ghitza wrote: > I find the current behaviour (which is fairly new) rather clear on this topic: > > ---------------------------------------------------------------------- > | Sage Version 4.1.1.rc0, Release Date: 2009-07-29 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > ********************************************************************** > * * > * Warning: this is a prerelease version, and it may be unstable. * > * * > ********************************************************************** > > > Best, > Alex
Sorry, I did not notice that had been added. I know I muted the idea before, but it seems someone has taken it up. Dave > On Sun, Aug 2, 2009 at 8:59 PM, Dr. David Kirkby<david.kir...@onetel.net> > wrote: >> I think any development release should clearly state it is a development >> release i.e. in big letters it comes up >> >> >> WARNING - THIS IS A DEVELOPMENT RELEASE FOR DEVELOPERS >> WARNING - DO NOT TRUST ANY RESULTS FROM THIS >> >> I don't know if we could do that automatically, based on the name of the >> build directory. i.e. if it contains 'rc0', 'rc1', 'rc2', 'alpha0', >> 'alpha1', then such a warning was automatically generated. >> >> What do people think of that idea? If its felt useful, I could create a >> Trac ticket for it. As for how to implement it, I am less sure, as I >> don't know enough about the build process. But it can't be rocket >> science to come up with some solution to this. (Anyway, I would not be >> surprised if some Sage developer was a rocket scientist!) >> >> >> >> Dave >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
