diff options
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/FOR-RELEASE | 24 | ||||
| -rw-r--r-- | admin/notes/years | 45 |
2 files changed, 61 insertions, 8 deletions
diff --git a/admin/FOR-RELEASE b/admin/FOR-RELEASE index b0169008af0..c1e91ff9595 100644 --- a/admin/FOR-RELEASE +++ b/admin/FOR-RELEASE | |||
| @@ -93,11 +93,19 @@ you're going to handle. | |||
| 93 | 93 | ||
| 94 | DIRECTORY STATUS IN CHARGE | 94 | DIRECTORY STATUS IN CHARGE |
| 95 | --------- ------ --------- | 95 | --------- ------ --------- |
| 96 | lisp/international working Kenichi Handa | 96 | leim working Kenichi Handa |
| 97 | lisp/languages working Kenichi Handa | 97 | lisp/calc done Thien-Thi Nguyen |
| 98 | lisp/net working Thien-Thi Nguyen | 98 | lisp/calendar working Glenn Morris |
| 99 | lisp/emulation done Thien-Thi Nguyen | ||
| 100 | lisp/eshell working Thien-Thi Nguyen | ||
| 101 | lisp/international done Kenichi Handa | ||
| 102 | lisp/languages done Kenichi Handa | ||
| 103 | lisp/mh-e done Thien-Thi Nguyen | ||
| 104 | lisp/net done Thien-Thi Nguyen | ||
| 99 | lisp/play done Thien-Thi Nguyen | 105 | lisp/play done Thien-Thi Nguyen |
| 100 | lisp/term working Thien-Thi Nguyen | 106 | lisp/term done Thien-Thi Nguyen |
| 107 | lisp/toolbar done Thien-Thi Nguyen | ||
| 108 | lisp/url working Thien-Thi Nguyen | ||
| 101 | 109 | ||
| 102 | ** Update AUTHORS. | 110 | ** Update AUTHORS. |
| 103 | 111 | ||
| @@ -216,10 +224,10 @@ lispref/windows.texi "Luc Teirlinck" Chong Yidong | |||
| 216 | 224 | ||
| 217 | ** Check the Emacs Tutorial. | 225 | ** Check the Emacs Tutorial. |
| 218 | 226 | ||
| 219 | The first line of every tutorial must begin with a sentence saying | 227 | The first line of every tutorial must begin with text ending in a period |
| 220 | "Emacs Tutorial" in the respective language. This should be followed | 228 | (".", ASCII 0x2E) saying "Emacs Tutorial" in the respective language. |
| 221 | by "See end for copying conditions", likewise in the respective | 229 | This should be followed by "See end for copying conditions", likewise |
| 222 | language. | 230 | in the respective language. |
| 223 | 231 | ||
| 224 | After each file name, on the same line or the following line, come the | 232 | After each file name, on the same line or the following line, come the |
| 225 | names of the people who have checked it. | 233 | names of the people who have checked it. |
diff --git a/admin/notes/years b/admin/notes/years new file mode 100644 index 00000000000..72f217e925d --- /dev/null +++ b/admin/notes/years | |||
| @@ -0,0 +1,45 @@ | |||
| 1 | How to Maintain Copyright Years for GNU Emacs | ||
| 2 | |||
| 3 | |||
| 4 | Principle: Individual files need to have the year of the release | ||
| 5 | in the copyright notice if there is significant change. | ||
| 6 | |||
| 7 | |||
| 8 | Practice: | ||
| 9 | |||
| 10 | - individual files | ||
| 11 | - each must be examined, along w/ its history, by a human | ||
| 12 | - automated tools facilitate but can never replace this process | ||
| 13 | |||
| 14 | - year of the release | ||
| 15 | - may be different from year of file introduction, | ||
| 16 | or year of last significant change | ||
| 17 | - sometimes the release year slips, leaving a file w/ prematurely | ||
| 18 | marked release year => need update (e.g., s/2004/2005/ for Emacs 22) | ||
| 19 | - intervening years (between releases) are not valid and may cause | ||
| 20 | embarrassment later in case of dispute => remove (however, see next) | ||
| 21 | - years for new files (merged, contributed) that have been separately | ||
| 22 | published are valid even if between releases => leave alone | ||
| 23 | |||
| 24 | - significant change | ||
| 25 | - insignificant | ||
| 26 | - whitespace | ||
| 27 | - copyright notice | ||
| 28 | - version control tags | ||
| 29 | - simple var/func renaming | ||
| 30 | - in-file reorganization/reordering | ||
| 31 | - typos | ||
| 32 | - small bugfixes | ||
| 33 | - small docfixes | ||
| 34 | - filename renaming | ||
| 35 | - most everything else is significant | ||
| 36 | - change to interface | ||
| 37 | - change in functionality | ||
| 38 | - new file | ||
| 39 | - many small changes may be significant in aggregate | ||
| 40 | |||
| 41 | - when in doubt, ask (and update these guidelines -- thanks!) | ||
| 42 | |||
| 43 | - sometimes people make mistakes | ||
| 44 | - if they have not read these guidelines, point them here | ||
| 45 | - if the guidelines are not helpful, improve the guidelines | ||