Timothy Clemans wrote:
> On Sun, Aug 2, 2009 at 4:10 AM, Dr. David Kirkby<david.kir...@onetel.net> 
> wrote:
>> 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 really like the firmness of that warning over what's currently in Sage.


I tried arguing this one before, but I appeared to have lost.

I personally feel some users wont even know what a 'prerelease' version 
is, whereas saying not to trust any results makes  it much clearer.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to