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.|
-
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() fo
On Sun, Aug 2, 2009 at 4:10 AM, Dr. David Kirkby 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
Timothy Clemans wrote:
> On Sun, Aug 2, 2009 at 4:10 AM, Dr. David Kirkby
> wrote:
>> Alex Ghitza wrote:
>>> I find the current behaviour (which is fairly new) rather clear on this
>>> topic:
>>>
>>> --
>>> | Sage Version 4.1.1.
On Aug 2, 8:32 am, "Dr. David Kirkby" wrote:
> Timothy Clemans wrote:
> > On Sun, Aug 2, 2009 at 4:10 AM, Dr. David Kirkby
> > wrote:
> >> Alex Ghitza wrote:
> >>> I find the current behaviour (which is fairly new) rather clear on this
> >>> topic:
>
> >>> --
John H Palmieri wrote:
>> I tried arguing this one before, but I appeared to have lost.
>
> No, last time you seemed to agree with it -- see the previous thread:
> http://groups.google.com/group/sage-devel/browse_thread/thread/b3e57f934ee83c79?tvc=2
>
> As far as the new suggestion ("WARNING ..
On Aug 2, 11:19 am, "Dr. David Kirkby"
wrote:
>
> If there were only pre-release versions of Sage available, and no stable
> release, then a less prominent message may be ok. But when there are
> stable releases, and someone is using one that has not had much testing,
> I believe that should be d
John H Palmieri wrote:
> On Aug 2, 11:19 am, "Dr. David Kirkby"
> wrote:
>> If there were only pre-release versions of Sage available, and no stable
>> release, then a less prominent message may be ok. But when there are
>> stable releases, and someone is using one that has not had much testing,
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
On Sun, Aug 2, 2009 at 12:44 PM, Dr. David
Kirkby wrote:
>
> John H Palmieri wrote:
>> On Aug 2, 11:19 am, "Dr. David Kirkby"
>> wrote:
>>> If there were only pre-release versions of Sage available, and no stable
>>> release, then a less prominent message may be ok. But when there are
>>> stable
I like Tim's suggestion. "Warning" in small letters sounds a little
timid.
Kwankyu Lee
--~--~-~--~~~---~--~~
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.c
Tim Lahey wrote:
> 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.
It's an improvement I would agree.
I also agree lower case is easier to read, but one is a bit less likely
to read
Hi David,
On Mon, Aug 3, 2009 at 4:19 AM, Dr. David Kirkby wrote:
>
> John H Palmieri wrote:
>
>>> I tried arguing this one before, but I appeared to have lost.
>>
>> No, last time you seemed to agree with it -- see the previous thread:
>> http://groups.google.com/group/sage-devel/browse_thread/t
2009/8/3 Minh Nguyen :
> I find that words in all capitals are much harder to read than words
> with title case. My comment about "hurting my ears" was in relation to
> using all capitals to denote shouting out loud. One of the down sides
> of text-based communication is that one needs to first t
Dr. David Kirkby wrote:
> John H Palmieri wrote:
>> On Aug 2, 11:19 am, "Dr. David Kirkby"
>> wrote:
>>> If there were only pre-release versions of Sage available, and no stable
>>> release, then a less prominent message may be ok. But when there are
>>> stable releases, and someone is using one
Hi,
My feeling is that adding the sentence
"WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE"
to a prerelease but not for a stable Sage version evokes that we can
trust all the results from the stable one. But I'm sure there is still
one bug to be fixed even in a stable Sage version.
On Mon, Aug 3, 2009 at 7:29 AM, slabbe wrote:
>
> Hi,
>
> My feeling is that adding the sentence
>
> "WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE"
>
> to a prerelease but not for a stable Sage version evokes that we can
> trust all the results from the stable one.
>
+1. It definit
On Aug 2, 2009, at 11:52 AM, John H Palmieri wrote:
>
> On Aug 2, 11:19 am, "Dr. David Kirkby"
> wrote:
>>
>> If there were only pre-release versions of Sage available, and no
>> stable
>> release, then a less prominent message may be ok. But when there are
>> stable releases, and someone is u
18 matches
Mail list logo
