blob: 8dd9677663ac44227b862e1b0a2940e46c9a1c8b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
-*- outline -*-
This is an outline of how to make a release for rt-liberation via GNU
ELPA.
* compile
Check for and correct compile-time errors and warnings.
* version
In order for the ELPA system to trigger a release the version number
in the comment header of rt-liberation.el must be incremented.
* Good News
Update the NEWS file to tell all of the people the Good News.
* documentation
Update the manual, compile it, and update the copy of the info file in
the root directory so that ELPA can install it.
Compile an HTML version of the manual and update it on the Website:
$ cvs commit -m "update manual" rt-liber.html
$ cvs commit -m "update website" index.html
* push
Push these updates to the git repo.
* tag
Tag the release with the ELPA version number, then push that tag to
the VCS:
$ git tag -a 2.2 -m "2.2"
$ git push --tags origin "2.2"
* ELPA
Merge the changes into the local externals/rt-liberation (git will
complain) and then push the changes to externals/rt-liberation on
elpa.git with:
$ git push
...as long as externals/rt-liberation has the right remote and merge
setup.
|
