When to post patches where [was Re: list-mode.el patch]
Stephen J. Turnbull
stephen at xemacs.org
Thu Dec 29 22:45:02 EST 2005
>>>>> "davep" == David A Panariti <davep.xemacs at meduseld.net> writes:
davep> As a point of information for me: this is dumped lisp code
davep> for a beta version. Should this be posted here or to
Patches that you are submitting for direct application to any of our
distributions (stable, beta, or packages) SHOULD _always_ go to
xemacs-patches. For the core distribution, you SHOULD indicate where
the patch is intended to be applied (stable aka 21.4 or unstable aka
21.5 or both), and if both, which distribution the patch was made
Patches that you are submitting as "proof-of-concept" to facilitate
discussion, but you believe are not ready for prime time as is, SHOULD
go _only_ to xemacs-beta.
For new features and UI changes, you MAY cross-post when you believe
that discussion of the costs and benefits is important, but if the
consensus is that the change is a good one, the patch may be ready to
go as-is. This is your call.
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
More information about the XEmacs-Beta