aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes
diff options
context:
space:
mode:
authorThien-Thi Nguyen2005-05-18 10:54:34 +0000
committerThien-Thi Nguyen2005-05-18 10:54:34 +0000
commite58414596cfbf3d003e7c4b9fcf3b7ece14e0b58 (patch)
tree0ec90ea53457a11bf8bc088f2b8c1efbcbadfa80 /admin/notes
parent1902b5b60b3d112673c411e474ce983a29133b63 (diff)
downloademacs-e58414596cfbf3d003e7c4b9fcf3b7ece14e0b58.tar.gz
emacs-e58414596cfbf3d003e7c4b9fcf3b7ece14e0b58.zip
Initial revision
Diffstat (limited to 'admin/notes')
-rw-r--r--admin/notes/years45
1 files changed, 45 insertions, 0 deletions
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 @@
1How to Maintain Copyright Years for GNU Emacs
2
3
4Principle: Individual files need to have the year of the release
5 in the copyright notice if there is significant change.
6
7
8Practice:
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