On Aug 20, 2007, at 9:18 AM, Nicholas Alexander wrote:
> >> - A new "if you work on something it should be in trac" rule: Instead >> of submitting patches directly to William you should create >> tickets in >> Sage's trac. So write William an Email and get a track account. >> - I volunteered to take care of Sage's trac installation and do bug >> triage and attempt to coordinate fixes. We should really avoid >> letting >> bugs get stale in trac and also make sure that we close tickets for >> issues that have been fixed either accidentally or via some other >> patch. Obviously if you like to help out let me know. > > One thing that I think has helped sage enormously is inline doctests > that are executed frequently. Well-formed trac reports more or less > include doctests, i.e. the offending code, but these "failtests" are > never executed. Would it be possible to "doctest trac" to find bugs > that have been incidentally closed, etc? > > On an unrelated note, is there a way to interface to trac via email? > I find that submitting bug reports via the web interface is far away > from my development environment; my email client is not. We are looking into using trac for the Unv. Washington Math Dept. help system, and if no one finds a way to submit bug reports via email, I will be writing one (it doesn't look to hard) as that is an essential requirement for us. +1 for the mercial plugin as well. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
