Re: related to an XEmacs BTS

Stephen> However, if we make any serious effort at entering Stephen> outstanding reports, say from the last year, I'll bet we can Stephen> easily get a couple hundred issues. How about the strategy of just entering new bugs and old bugs that the bug reporter feels like should go into to bug tracker. This would mean having bugs reported and handled in two places but it wouldn't burden this try to start with a lot of administrative work. There will probably be some of that anyway. Stephen> We are going to need workers to enter the issues, classify Stephen> and prioritize them, identify duplicates, link issues to Stephen> relevant mailing list threads, and close fixed, bogus, or Stephen> unfixable issues. These are tasks that need to be done if you handle bugs whatever system, manual or automated, is in use!? Stephen> Would anybody like to do that? People who volunteer to do Stephen> that work get two votes on the choice of tracker. :-) To me that seems essential for every developer to care about. I'm sure though you got a point in that there needs to be one or a few people who feels a bit more for maintaining the tracker. Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta