aniani/elinks
1
0
Fork 0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00
Code

release: more like what I actually did with 0.12pre1

Browse Source 
In particular:
- mkdist takes options and need not be run at elinks.cz
- git push just the single tag, rather than all --tags
- explicitly avoid multipart/signed
- add the release date from the elinks-users archive to NEWS
- update download.txt, release.html, and bugzilla/milestones/elinks.html
This commit is contained in:
Kalle Olavi Niemitalo 2008-07-02 00:58:04 +03:00 committed by Kalle Olavi Niemitalo
parent d5dcdb4d92
commit 45f237a26c
1 changed files with 32 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
doc/release.txt
View File

@ -4,14 +4,13 @@ Release check list
When releasing a new version When releasing a new version
---------------------------- ----------------------------
1. Tasks in the elinks module: 1. Tasks in the elinks module (part 1):
- Go over the changes since the last release. Use git-shortlog as a template. - Go over the changes since the last release. Use git-shortlog as a template.
Write a small changelog highlighting the most important changes. Changes Write a small changelog highlighting the most important changes. Changes
by new contributors are always important! by new contributors are always important!
- Update NEWS file and commit. Remember to add the new version number! - Update NEWS file and commit. Remember to add the new version number!
Don't add the release date yet though; it will be added after the release, Don't add the release date yet though; you will add it in a later step.
from the date in the mailing list archives.
- Change VERSION in the top of configure.in to hold the new version number. - Change VERSION in the top of configure.in to hold the new version number.
- Update the manpages so the will have the new release number by first - Update the manpages so the will have the new release number by first
building the source, followed by making the `update-man' target in doc/. building the source, followed by making the `update-man' target in doc/.
@ -22,58 +21,73 @@ When releasing a new version
$ git tag -s -F changelog.file elinks-X.X.X $ git tag -s -F changelog.file elinks-X.X.X
- Run script to create new tarballs (both .gz and .bz2).
$ contrib/mkdist -g "$PWD/.git" -r elinks-X.X.X -l X.X.X
This step also builds the elinks binary and documentation based on
the label, and that might fail because of some bug, so it's best to
do this before pushing anything.
- Create ASCII armored signature files.
$ gpg -b --armor elinks-X.X.X.tar.bz2
$ gpg -b --armor elinks-X.X.X.tar.gz
- Append ".GIT" to the VERSION variable in the top of configure.in. - Append ".GIT" to the VERSION variable in the top of configure.in.
- Commit only this change. - Commit only this change.
- Push these changes plus tag using: - Push these changes plus tag using:
$ git push $ git push
$ git push --tags $ git push tag elinks-X.X.X
2. Tasks on http://elinks.cz/ (part 1): 2. Tasks on http://elinks.cz/ (part 1):
- Wait until the tag etc. has been synced or force a sync of the repository - Wait until the tag etc. has been synced or force a sync of the repository
at http://elinks.cz/elinks.git/. at http://elinks.cz/elinks.git/.
- Run script to create new tarballs (both .gz and .bz2).
$ mkdist elinks-X.X.X X.X.X -r
3. Tasks on localhost: 3. Tasks on localhost:
- Download new tarballs and create ASCII armored signature files. - Copy the elinks-X.X.X.tar.* files to http://elinks.cz/download/.
- Send announcement to elinks-users mailing list. Do not format it
as multipart/signed because the linuxfromscratch archive does not
display such messages properly.
- Wait for the announcement to hit the elinks-users mailing list archive.
$ gpg -b --armor elinks-X.X.X.tar.bz2 4. Tasks in the elinks module (part 2):
$ gpg -b --armor elinks-X.X.X.tar.gz
- Copy the elinks-X.X.X.tar.*.asc files to http://elinks.cz/download/. - Add the release date from the mailing list archive to NEWS.
- Send announcement to elinks-users mailing list. - Commit and push that change.
4. Tasks in the elinks-web module: 5. Tasks in the elinks-web module:
- Change the version and release data in the start of website.conf. - Change the version and release data in the start of website.conf.
- Wait for the announcement to hit the elinks-users mailing list archive. Also change download.txt if necessary.
- Add paraphrased version of the first paragraph of the release announcement - Add paraphrased version of the first paragraph of the release announcement
as a news entry in news/latest.txt. Make the entry link to both the as a news entry in news/latest.txt. Make the entry link to both the
archived announcement from linuxfromscratch.org and gmane.org using the archived announcement from linuxfromscratch.org and gmane.org using the
"magic numbers" expanded by the macro. Possibly, move the cut-off markers "magic numbers" expanded by the macro. Possibly, move the cut-off markers
that control which news entries to display on the front page. that control which news entries to display on the front page.
- Rebuild index.html, download.html, news.html, and news.rss. - Rebuild index.html, download.html, news.html, news.rss, and release.html.
- Update bugzilla/milestones/elinks.html if the release corresponds
to a reached milestone.
- Commit the updates HTML and asciidoc files. - Commit the updates HTML and asciidoc files.
- Push the commits. - Push the commits.
5. Tasks on http://elinks.cz/ (part 2): 6. Tasks on http://elinks.cz/ (part 2):
- Wait until the elinks-web module has been synced or force a sync of the - Wait until the elinks-web module has been synced or force a sync of the
repository. repository.
- Checkout the new updated webpages. - Checkout the new updated webpages.
6. Tasks on http://bugzilla.elinks.cz/: 7. Tasks on http://bugzilla.elinks.cz/:
- Add the new version. - Add the new version.
- Add a comment to each bug fixed in this version. If some of them - Add a comment to each bug fixed in this version. If some of them
are already VERIFIED, change them to CLOSED, unless they are also are already VERIFIED, change them to CLOSED, unless they are also
waiting for a release in another branch. waiting for a release in another branch.
7. Tasks external sites and resources: 8. Tasks external sites and resources:
- Add a new release to the freshmeat.net page. - Add a new release to the freshmeat.net page.
- Change topic of #elinks - Change topic of #elinks