On Aug 2, 2009, at 3:44 PM, Dr. David Kirkby wrote:
> > I can imagine a scenario where a user installs a pre-release > version, as > it fixes a problem he has. If Sage is working well for him, he > probably > wont bother updating it. Then others use his software, and don't give > the warning too much thought, since it was there the first time they > used it. > > IMHO, hammering home the nature of the build is important. > > > As a matter of interest, do any others have a view on which is best? > > 1) > ********************************************************************** > * * > * Warning: this is a prerelease version, and it may be unstable. * > * * > ********************************************************************** > > 2) > > ********************************************************************** > * WARNING - THIS IS A DEVELOPMENT RELEASE FOR DEVELOPERS * > * WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE * > ********************************************************************** > > So what is it, (1) or (2) ? > How about, WARNING: This is a prerelease version, and it may be unstable. That way, it stands out, but is still easy to read. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo http://www.linkedin.com/in/timlahey --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
