Hi Florent, On Sun, Mar 7, 2010 at 10:20 PM, Florent Hivert <florent.hiv...@univ-rouen.fr> wrote:
<SNIP> > Note that I've no idea how hard it is to implement in trac, neither if we > have the necessary hardware to support this load. >From reading the Sage merge script, I think one could use that script or write something along similar lines to implement a (simple) proof-of-concept continuous buildbot. That is, without adding any new fields to trac. I just want to point out that the current number of fields on a trac ticket can overwhelm a beginner, indeed anyone. More fields added would mean more time spent thinking about what information to add to which field. In many cases, one could easily write a lot of information clearly and concisely as a ticket comment. If the information is critical for reviewing a ticket, such information could be written in the ticket description. If you have been following how David Kirkby writes his descriptions for Solaris and portability tickets, you would see what I mean. -- Regards Minh Van Nguyen -- 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
