| 1 |
These instructions are for building a new lifelines |
| 2 |
release, in your cvs working directory, and actually |
| 3 |
releasing it. |
| 4 |
|
| 5 |
Fetch latest cvs if desired, eg |
| 6 |
$ cvs -z3 up -d |
| 7 |
|
| 8 |
Edit the version number, setting it to the new release: |
| 9 |
(Running, eg, "cd build; sh setversions.sh 3.0.19; cd .." does this) |
| 10 |
(NB: setversions.sh requires bash3) |
| 11 |
NEWS |
| 12 |
INSTALL |
| 13 |
README |
| 14 |
configure.ac |
| 15 |
build/rpm/lifelines.spec |
| 16 |
src/hdrs/version.h |
| 17 |
build/msvc6/btedit/btedit.rc (4 occurrences) |
| 18 |
build/msvc6/dbverify/dbVerify.rc (4 occurrences) |
| 19 |
build/msvc6/llexec/llexec.rc (4 occurrences) |
| 20 |
build/msvc6/llines/llines.rc (4 occurrences) |
| 21 |
docs/ll-devguide.xml (2 occurrences) |
| 22 |
docs/ll-reportmanual.xml (2 occurrences) |
| 23 |
docs/ll-userguide.xml (2 occurrences) |
| 24 |
docs/llines.1 (& year & month as well) |
| 25 |
|
| 26 |
Run autotools: |
| 27 |
$ sh autogen.sh |
| 28 |
|
| 29 |
Note: There are several reports which do not build |
| 30 |
correctly in UTF-8 locale. Therefore, if you use |
| 31 |
a UTF-8 locale, do something like so: |
| 32 |
export LANG=en_US.ISO-8859-1 |
| 33 |
|
| 34 |
Build local copy in ./bld subdirectory: |
| 35 |
$ rm -rf bld |
| 36 |
$ mkdir bld |
| 37 |
$ cd bld |
| 38 |
$ ../configure |
| 39 |
$ make |
| 40 |
|
| 41 |
Update master message catalog template (for i18n): |
| 42 |
$ mv ../po/lifelines.pot ../po/lifelines.old.pot |
| 43 |
$ cd po |
| 44 |
$ make lifelines.pot |
| 45 |
$ cd .. |
| 46 |
|
| 47 |
Build distribution tarball: |
| 48 |
$ make dist |
| 49 |
$ cd .. |
| 50 |
|
| 51 |
Add an entry mentioning the new version in the |
| 52 |
ChangeLog |
| 53 |
|
| 54 |
Commit changes (new version number, new message catalogs): |
| 55 |
$ cvs -z3 ci |
| 56 |
|
| 57 |
Announce new version to Free Translation Project. |
| 58 |
Per: http://www.iro.umontreal.ca/translation/HTML/maintainers.html |
| 59 |
<Merely send the URL of a packaged distribution to |
| 60 |
[email protected]. Use the string |
| 61 |
"DOMAIN-VERSION.pot" somewhere in the subject line |
| 62 |
of your invoice. Beware that a POT file may only |
| 63 |
be processed once by the Translation Project.> |
| 64 |
Free Translation Project page for lifelines: |
| 65 |
http://www.iro.umontreal.ca/translation/registry.cgi?domain=lifelines |
| 66 |
|
| 67 |
Build any other files (eg, other tarball formats, |
| 68 |
MS-Windows binary packages, rpm packages). |
| 69 |
|
| 70 |
rpm: See README.MAINTAINERS.rpm |
| 71 |
|
| 72 |
debian: lifelines is a supported debian package |
| 73 |
and has a debian maintainer (q.v.) |
| 74 |
|
| 75 |
MS-Windows: See README.MAINTAINERS.win32 |
| 76 |
|
| 77 |
|
| 78 |
Go to lifelines admin page, and create a new |
| 79 |
beta release. Paste in top part of ./NEWS file |
| 80 |
for ChangeLog entry, and copy & paste release |
| 81 |
notes from previous beta release, updating md5 |
| 82 |
signatures to those of new release files. |
| 83 |
|
| 84 |
Upload the release files (tarball etc.) to |
| 85 |
uploads.sourceforge.net. From the release page |
| 86 |
(above, opened from project admin), refresh |
| 87 |
and attach the release files, and set properties |
| 88 |
appropriately (can look at previous releases to |
| 89 |
see how to set them). |
| 90 |
|
| 91 |
Tag the cvs source via (for example, for version 3.0.25) |
| 92 |
cvs tag v3_0_25 |
| 93 |
|
| 94 |
Send an announcement to the LINES-L mailing list |
| 95 |
(send to user LINES-L at domain LISTSERV.NODAK.EDU). |
| 96 |
|
| 97 |
|