Re: Bug tracker: next steps

Stephen> But regarding the reasons advertised in this thread, it's not Stephen> going to help with archived bugs for years, and it's not likely Stephen> to help folks like Hans much because I think it's going to be Stephen> file and forget for most issues, unless we have a volunteer who Stephen> bugs developers to work on stuff. It also provides a place for new people to dive in and help. I'm sure Stephen is familiar with the "for faster service review five" policy some of the Python folks abide by. If you submit a patch or bug fix and you'd like it processed in a more expedient fashion, simply review five other open bugs/patches then send an email to the list (xemacs-beta in this case) identify the issue numbers of the items you reviewed and what bug/patch the author wants expedited. "Review" in this case can mean just about anything helpful: * I applied the patch in my XYZ environment. It worked (or didn't work) for me. * There are no changes to the documentation or test cases. * I attached another patch with some extra documentation. * I think this change could be better done this other way. * etc. Skip _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta