On Mar 19, 2010, at 3:18 AM, Dima Pasechnik wrote:
Craig,
[...]
For the record, I think it's pretty unreasonable to *require* Sage
developers to test on anything but their own machine -- but I *do*
think it's very reasonable to ask them to help fix problems with
their
patches that arise on other architectures, especially if we can give
them a place to ssh and try things out.
well, as soon as it it is past vanilla Python/Cython, it becomes
unclear whether
a given change will not break functionality on another platform.
So I do not see how in this case one can limit testing to one
platform only.
E.g. I went out of my way to test an upgrade of the GAP spkg on any
platform I could get my hands on.
For spkgs, changes to shell scripts, etc. a it is much more important
to test on a wide variety of platforms. Fortunately, most
contributions are plain vanilla Python/Cython.
Thanks for bringing this up, this is an example of what separates (in
my mind) the "sage-build" level stuff from the "sage-devel" level stuff.
- Robert
--
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
URL: http://www.sagemath.org
To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or
reply to this email with the words "REMOVE ME" as the subject.
