4 When releasing a new version
5 ----------------------------
7 1. Tasks in the elinks module:
9 - Go over the changes since the last release. Use git-shortlog as a template.
10 Write a small changelog highlighting the most important changes. Changes
11 by new contributors are always important!
12 - Update NEWS file and commit. Remember to add the new version number!
13 Don't add the release date yet though; it will be added after the release,
14 from the date in the mailing list archives.
15 - Change VERSION in the top of configure.in to hold the new version number.
16 - Commit only this change.
17 - Create a signed tag having the version ("ELinks X.X.X") as the subject and
18 using the changelog create above as the body. Use something like:
20 $ git tag -s -F changelog.file elinks-X.X.X
22 - Append ".GIT" to the VERSION variable in the top of configure.in.
23 - Commit only this change.
24 - Push these changes plus tag using:
29 2. Tasks on http://elinks.cz/ (part 1):
31 - Wait until the tag etc. has been synced or force a sync of the repository
32 at http://elinks.cz/elinks.git/.
33 - Run script to create new tarballs (both .gz and .bz2).
35 $ mkdist elinks-X.X.X X.X.X -r
37 3. Tasks on localhost:
39 - Download new tarballs and create ASCII armored signature files.
41 $ gpg -b --armor elinks-X.X.X.tar.bz2
42 $ gpg -b --armor elinks-X.X.X.tar.gz
44 - Copy the elinks-X.X.X.tar.*.asc files to http://elinks.cz/download/.
45 - Send announcement to elinks-users mailing list.
47 4. Tasks in the elinks-web module:
49 - Change the version and release data in the start of website.conf.
50 - Wait for the announcement to hit the elinks-users mailing list archive.
51 - Add paraphrased version of the first paragraph of the release announcement
52 as a news entry in news/latest.txt. Make the entry link to both the
53 archived announcement from linuxfromscratch.org and gmane.org using the
54 "magic numbers" expanded by the macro. Possibly, move the cut-off markers
55 that control which news entries to display on the front page.
56 - Rebuild index.html, download.html, news.html, and news.rss.
57 - Commit the updates HTML and asciidoc files.
60 5. Tasks on http://elinks.cz/ (part 2):
62 - Wait until the elinks-web module has been synced or force a sync of the
64 - Checkout the new updated webpages.
66 6. Tasks on http://bugzilla.elinks.cz/:
68 - Add the new version.
69 - Add a comment to each bug fixed in this version. If some of them
70 are already VERIFIED, change them to CLOSED, unless they are also
71 waiting for a release in another branch.
73 7. Tasks external sites and resources:
75 - Add a new release to the freshmeat.net page.
76 - Change topic of #elinks
77 - (Request update of FSFs free software directory).
78 - (Update current version on wikipedia).
80 When releasing a new stable branch
81 ----------------------------------
83 (I only vaguely remember this process. --jonas)
85 1. Tasks on localhost:
87 - Locally clone the freezed repository to a new repository that will contain
88 the new stable branch.
89 - Unfreeze the repository that was cloned by changing the VERSION variable in
90 configure.in to the version of the new unstable branch (remember the
91 ending ".GIT"), commit, and push.
92 - Add new remote branch that will track the new stable "trunk". It should
93 basically be the push URL of the cloned repository with "#elinks-X.X"
95 - Push to this new remote branch to create it.
96 - Perform the normal version release tasks described above in this new
99 2. Tasks on http://elinks.cz/:
101 - Update http://elinks.cz/download/*-current-* tarball links to point to the
104 3. Tasks external sites and resources:
106 - Add a new branch to the freshmeat.net page.