[61ec1a]: gemrb / docs / en / Release.txt  Maximize  Restore  History

Download this file

86 lines (64 with data), 2.7 kB

 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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
How to make a release
*********************
Preparing and testing GIT
=========================
* Make sure that version numbers in
configure.in
gemrb/includes/globals.h
are correct for the upcoming version.
* Update NEWS with highlights since the last release
* Make sure that GemRB GIT is in compilable and runnable state
- download a clean GIT tree and test it.
- Make distribution .tar.gz (see Source release below) and test it as well -
especially make sure all needed files are included.
* Tag current GIT to version number e.g. v0.9.0
i.e. in the gemrb root directory do
ver=0.9.0
git tag -a -m "GemRB $ver" v$ver
git push origin v$ver
* Update from GIT to the tagged version
git checkout v$ver
* After you're done, update the version with a -git suffix, so it will be
easier to tell if people are running release builds or not
Source release
==============
* via cmake/autotools:
make dist
Linux binary release
====================
./autogen.sh
./configure --prefix=/usr/local
make
make install DESTDIR=/tmp/fakeroot
cd /tmp/fakeroot/usr/local
copy ~/GemRB-binary.cfg over etc/GemRB.cfg, rename to etc/gemrb.cfg
strip bin/gemrb lib/* lib/gemrb/*
sudo chown -R 0:0 *
sudo tar cvzf ../gemrb-0.2.5-linux_i386.tar.gz *
Windows binary release
======================
If gembot is around on IRC, ask it to make a build for the tagged revision:
gembot: force build --revision=701453842c7cb5783 nmake-msvc++10 release build
gembot: watch nmake-msvc++10
It will tell you where to see the report and on the last (upload) step,
there will also be a link for the binary download. Rename it, upload
it to the main sourceforge windows directory and mark it as default for
the platform.
Release and Announcements
=========================
* Write the release notes if necessary. They are mainly for packagers, so
create them if there are structural or build related changes. New config
options should also be mentioned here if they're not part of the changelog.
* Put the tarballs/binaries into Releases on SF
- go to the Files section
- click on the sources subdir
- add a new similarly-named folder
- use "add file" to upload the sources and release notes
- change the file properties to set the default platforms (under "view details")
* Test the downloads from sourceforge.net
* Announce on homepage, SF, #GemRB in channel and title, Happypenguin, LGDB and
Gibberlings3:
- our forum
- modding news (Avenger, Theacefes, Grim Squeaker, DavidW and cmorgan have access)
(a template is available in admin/announcement.template)
* Run admin/restart_news.sh to restart the NEWS cycle

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks