]>
Commit | Line | Data |
---|---|---|
cd1a2927 MT |
1 | Prerequisites |
2 | - have release right on sourceforge to be able to affect uploaded files to a release | |
3 | - have 'IPCop development Group' private gpg key (and password) to sign the patch, import the key with gpg --import (private key file name) | |
4 | - you can create your own key with whatever name you want and replace (temporarily!) the pub key in | |
5 | your box (/root/.gnupg/*) for testing your patch | |
6 | ||
7 | Build | |
8 | - ./make.sh changelog and commit : update doc/Changelog (include in the .iso) | |
9 | - ./make.sh build | |
10 | - ./make.sh dist : | |
11 | build source package by exporting from CVS, | |
12 | create a check-list of modified files in doc/updated-sources.txt | |
13 | - manually check all necessary files are include in updates/1.4.x/ROOTFILES.*.1.4.x comparing with /doc/updated-sources.txt | |
14 | - sign the patch with gpg --local-user "IPCop Development Group" --sign ipcop-update-1.4.x.tgz (or with another name given to the key) | |
15 | - for the announce, files md5 are obtained with md5sum ipcop-* | |
16 | ||
17 | Sourceforge | |
18 | - in case of test files, rename them with rename 1.4.x 1.4.xtest *1.4.x* | |
19 | - upload files via ftp to upload.sourceforge.net in incoming directory | |
20 | (may need to have more than 30s inactivity timeout to be able to connect on sourceforge) | |
21 | - add a new release | |
22 | for test file, status active under "IPCop test versions" package | |
23 | for official release, status active under "IPCop" package | |
24 | affect uploaded files (web interface Files Release System) on the release | |
25 | add Changelog and text abstract at the release | |
26 | - control file size under Files web page once files are affected to the package | |
27 | - with ssh, update every patch list on shell.sourceforge.net /home/groups/i/ip/ipcop/htdocs/patches preceding the previous v1.4.x version with : | |
28 | the content of updates/1.4x/information (and add the link to the release on sourceforge at the end of the line) | |
29 | - add a new entry corresponding to the next version number in the patch list with only "----START LIST----" inside | |
30 | chmod 664 the file | |
31 | - In Tracker, Tracker administration, bugs, add a new group corresponding to the version number | |
32 | ||
33 | Update CVS : | |
34 | - with the tag of the release | |
35 | cvs tag IPCOP_v1_4_(x)_FINAL | |
36 | ||
37 | - bump VERSION and PREVIOUSTAG in make.sh | |
38 | - ./make.sh newupdate | |
39 | will add a new directory in updates corresponding to the new version number with files: | |
40 | information (Id number should be 003 for VERSION=1.4.3) | |
41 | ROOTFILES.alpha-1.4.x | |
42 | ROOTFILES.i386-1.4.x | |
43 | setup | |
44 | .cvsignore (containing patch.tar.gz ) | |
45 | ||
46 | www.ipcop.org | |
47 | - update with doc/packages-list.txt | |
48 | http://www.ipcop.org/modules.php?op=modload&name=phpWiki&file=index&pagename=IPCopSoftwares | |
49 | ||
50 | News | |
51 | - send news on user devel announce lists (subscribe to announce before if necessary) |