Mercurial > hg > xemacs-beta

comparison etc/BETA @ 1044:911faaa82855

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-10-09 12:43:09 by stephent] describe Patches better <87wuor946u.fsf_-_@tleepslib.sk.tsukuba.ac.jp>
author stephent
date Wed, 09 Oct 2002 12:43:12 +0000
parents ccaf90c5a53a
children f00ca2822f4e
comparison
equal deleted inserted replaced
1043:ab78afb114ea 1044:911faaa82855
17 Currently all discussion of development issues, including bug reports 17 Currently all discussion of development issues, including bug reports
18 and coding discussion, takes place on the XEmacs Beta mailing list. 18 and coding discussion, takes place on the XEmacs Beta mailing list.
19 Only patches and administrative actions regarding patches are sent 19 Only patches and administrative actions regarding patches are sent
20 elsewhere (to the XEmacs Patches list). 20 elsewhere (to the XEmacs Patches list).
21 21
22 ** XEmacs Patches Mailing List 22 *** XEmacs Patches Mailing List
23 ============================== 23 -------------------------------
24 24
25 XEmacs Patches records proposed changes to XEmacs, and their 25 XEmacs Patches records proposed changes to XEmacs, and their
26 disposition. It is open subscription, but only patches and actions by 26 disposition. It is open subscription, and all patches that are
27 members of the XEmacs Review Board should be posted to this list. You 27 seriously proposed for inclusion in XEmacs should be posted here. You
28 can follow progress of your patch by subscribing to the mailing list 28 can follow progress of your patch by subscribing to the mailing list
29 or in the archives. 29 or in the archives.
30 30
31 ** List Administrivia 31 Besides patches, only actions by members of the XEmacs Review Board
32 ===================== 32 should be posted to this list. All discussion should be redirected to
33 XEmacs Beta or XEmacs Design.
34
35 *** XEmacs Design Mailing List
36 ------------------------------
37
38 XEmacs Design is for design discussions such as adding major features
39 or whole modules, or reimplementation of existing functions, to XEmacs.
40
41 *** List Administrivia
42 ----------------------
33 43
34 In the descriptions below, the word LIST (all uppercase) is a 44 In the descriptions below, the word LIST (all uppercase) is a
35 variable. Substitute "beta" or "patches" as appropriate (to get 45 variable. Substitute "beta", "design", or "patches" as appropriate
36 "xemacs-beta" as the mailbox for the XEmacs Beta mailing list, or 46 (to get "xemacs-beta" as the mailbox for the XEmacs Beta mailing list,
37 http://www.xemacs.org/Lists/#xemacs-beta for its URL). 47 or http://www.xemacs.org/Lists/#xemacs-beta for its URL).
38 48
39 The XEmacs mailing lists are managed by the Mailman mailing list 49 The XEmacs mailing lists are managed by the Mailman mailing list
40 package, and the usual Mailman commands work. Do not send mailing 50 package, and the usual Mailman commands work. Do not send mailing
41 list requests to the main address (xemacs-LIST@xemacs.org), always 51 list requests to the main address (xemacs-LIST@xemacs.org), always
42 send them to xemacs-LIST-request@xemacs.org. If you have problems 52 send them to xemacs-LIST-request@xemacs.org. If you have problems
44 XEmacs Mailing List manager <list-manager@xemacs.org> (the same 54 XEmacs Mailing List manager <list-manager@xemacs.org> (the same
45 mailbox, "list-manager", for all lists). All public mailing lists 55 mailbox, "list-manager", for all lists). All public mailing lists
46 have searchable archives. The URL is 56 have searchable archives. The URL is
47 57
48 http://list-archive.xemacs.org/xemacs-LIST 58 http://list-archive.xemacs.org/xemacs-LIST
59
60 Note that the xemacs-LIST-admin address is used internally by the
61 Mailman software; it is NOT a synonym for xemacs-LIST-request.
49 62
50 *** Managing your subscription via the Web 63 *** Managing your subscription via the Web
51 ------------------------------------------ 64 ------------------------------------------
52 65
53 Subscription, unsubscription, and options (such as digests and 66 Subscription, unsubscription, and options (such as digests and
360 ================= 373 =================
361 374
362 ** Creating patches for submission 375 ** Creating patches for submission
363 ================================== 376 ==================================
364 377
365 Patches to XEmacs should be mailed to <xemacs-patches@xemacs.org>. 378 All patches to XEmacs that are seriously proposed for inclusion (eg,
366 Each patch will be reviewed by the patches review board, and will be 379 bug fixes) should be mailed to <xemacs-patches@xemacs.org>. Each
380 patch will be reviewed by the patches review board, and will be
367 acknowledged and added to the distribution, or rejected with an 381 acknowledged and added to the distribution, or rejected with an
368 explanation. Progress of the patch is tracked on the XEmacs Patches 382 explanation. Progress of the patch is tracked on the XEmacs Patches
369 mailing list, which is open subscription. 383 mailing list, which is open subscription. (If a patch is simply
384 intended to facilitate discussion, "I mean something that works like
385 this but this is really rough", a CC to XEmacs Patches is optional,
386 but doesn't hurt.)
370 387
371 Patches to XEmacs Lisp packages should be sent to the maintainer of 388 Patches to XEmacs Lisp packages should be sent to the maintainer of
372 the package. If the maintainer is listed as `XEmacs Development Team' 389 the package. If the maintainer is listed as `XEmacs Development Team'
373 patches should be sent to <xemacs-patches@xemacs.org>. 390 patches should be sent to <xemacs-patches@xemacs.org>.
374 391
444 unless you're sure you'll follow up with a "real" patch, better to err 461 unless you're sure you'll follow up with a "real" patch, better to err
445 on the side of posting to xemacs-patches. 462 on the side of posting to xemacs-patches.
446 463
447 Discussion of the _content_ of the patch (ie responses to reviewer 464 Discussion of the _content_ of the patch (ie responses to reviewer
448 comments beyond "that's right, ok, I'll do it your way") should _always_ 465 comments beyond "that's right, ok, I'll do it your way") should _always_
449 be posted to xemacs-beta. (We may split xemacs-beta into code 466 be posted to xemacs-beta or to xemacs-design. If you're not sure
450 discussion and stuff that is more relevant to non-developer testers at 467 which is more appropriate, send it to xemacs-beta. That is the most
451 some point, but at this point xemacs-beta is the correct place for 468 widely read channel.
452 this.)
453 469
454 If discussion results in a bright idea and you come up with a new 470 If discussion results in a bright idea and you come up with a new
455 patch, normally you should post it to both mailing lists. The people 471 patch, normally you should post it to both mailing lists. The people
456 discussing on XEmacs Beta will want to know the outcome of the thread, 472 discussing on XEmacs Beta will want to know the outcome of the thread,
457 and you need to submit to XEmacs Patches as the "list of record." 473 and you need to submit to XEmacs Patches as the "list of record."
459 If the old patch has been applied to CVS, then just submit the new one 475 If the old patch has been applied to CVS, then just submit the new one
460 as usual. If it has not been applied, then it is best to submit a new 476 as usual. If it has not been applied, then it is best to submit a new
461 patch against CVS. If possible do this as a reply to the original 477 patch against CVS. If possible do this as a reply to the original
462 patch post, or something following it in the thread. (The point is to 478 patch post, or something following it in the thread. (The point is to
463 get the original patch post's Message-ID in your References header.) 479 get the original patch post's Message-ID in your References header.)
464 In this case, also use the keyword SUPERCEDES in the Subject header to 480 In this case, also use the keyword SUPERSEDES in the Subject header to
465 indicate that the old patch is no longer valid, and that this one 481 indicate that the old patch is no longer valid, and that this one
466 replaces it. 482 replaces it.
467 483
468 These rules will result in a fair number of cross posts, but we don't 484 These rules will result in a fair number of cross posts, but we don't
469 yet have a better way to handle that. 485 yet have a better way to handle that.