"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
If you think you're ready for it, feel free to apply for
reviewer
status (at xemacs-review(a)xemacs.org). FWIW, I won't veto it if others
are enthusiastic, but IMO the history of a couple of your recent
patches doesn't make a strong case that you have a reviewer's judgment
skills combined with the knowledge of XEmacs best practices that is
needed yet. If given that caveat you still think you're ready, go for
it. (Also, even if we decide to wait and see *now*, your name is on
my short list of candidates for the near future, and probably others'
lists as well.)
I don't have the confidence for anything but tiny patches.
There are too many larger details I don't know yet. I'd
rather have my changes reviewed.
An alternative to being a reviewer is to publish your patches in a
branch at alioth. That makes it easy for beta testers to incorporate
them in their builds and test them (vs. downloading and applying
patches), but of course is somewhat greater burden on you.
Do you mean a branch in /hg/xemacs/xemacs? I'm kind of afraid of hg
branches; I've made a few mistakes in the xemacs-gtk repo.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta