On Sat, Apr 25, 2009 at 08:50:50AM -0700, William Stein wrote:
> Just for the record, I hate when there is a looming patch over
> months of time whose main impact on Sage is to keep the rest of Sage
> from improving in quality. For example, with Bill Furnish working on
> symoblic for months, the main longterm impact on Sage was that
> nobody improved any of the calculus doctests.
Definitely. But with developers being mostly volunteers with other
time constraints this can't be completely avoided without preventing
any large scale refactoring. And, as any young software, Sage need
some of those.
> Two days ago I sat down to do some work on implementing general
> modules over a PID and decided to add some doctests to modules/*. I
> quickly found a *major* bug in categories/morphisms.py, and you
> better believe I fixed it and kept adding doctests.
Great. I am glad you did!
But please: *keep me updated about any such change as soon as
possible* so as to limit conflicts. Every late conflict resolution
just delays even further the final merge.
And for little doc fixes (typos, ...): I would much prefer if they
were just mentioned to me, and I would be glad to integrate them
directly in my patches.
Best,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send 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
-~----------~----~----~----~------~----~------~--~---
