File: release-method.txt

package info (click to toggle)
freeradius-client 1.1.6-7
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 2,048 kB
  • ctags: 504
  • sloc: sh: 8,504; ansic: 4,704; perl: 425; makefile: 86
file content (139 lines) | stat: -rw-r--r-- 2,952 bytes parent folder | download | duplicates (2)
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
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
# Version:      $Id: release-method.txt,v 1.2 2007/04/14 23:40:35 pnixon Exp $
#
#  This is NOT a shell script!
#
#  This file documents the methods used by the developers to perform a release of the software.
#
#  If you're not a developer, then you can ignore this file.
#
#
VERSION=1
REVISION=1

# cvs -d :pserver:USER@cvs.freeradius.org:/source checkout -P -d freeradius-client-$(VERSION).$(REVISION) radiusclient
cvs -d :pserver:USER@cvs.freeradius.org:/source checkout -P -d freeradius-client-1.1 radiusclient

#
#  Do NOT type 'configure', 'make', or anything else.
#  We presume that 
#
# cd freeradius-client-$(VERSION).$(REVISION)
cd freeradius-client-1.1

#
#  Create a branch for the release
#
cvs tag -b branch_1_1

#
#  Mark all of the files to be for the branch
#
cvs update -rbranch_1_1

#
#  remove $$ surrounding the $Date ... $
#  add any last-minute notes
#
vi doc/ChangeLog

#
#  Commit it (to the branch)
#
cvs commit doc/ChangeLog

#
#  Change version/revision numbers
#
vi configure.in
vi redhat/freeradius-client.spec
vi suse/freeradius-client.spec
vi debian/changelog
vi debian/rules

#
#  Re-build and commit the configure scripts and other autofoo
libtoolize --force
aclocal
automake -ac
autoconf
cvs commit

#
#  tag the files for the release,
#  which is a POINT release of the main release.
#
#  i.e. We may way a 0.7.1 release later, which will
#  be tagged 'release_0_7_1' on the branch for 0.7,
#  which is called 'branch_0_7'.
#
# cvs tag release_$(VERSION)_$(REVISION)_0
cvs tag release_1_1_0

#
#  Delete the CVS directories.
#
rm -rf `find . -name CVS -print`

#
#  Delete any temporary files.
#
rm -f `find . -name "*~" -print`

#
#  Visually inspect the source, to be sure it's clean.
#

cd ..

# tar jcf freeradius-client-$(VERSION).$(REVISION).tar.bz2 freeradius-client-$(VERSION).$(REVISION)
tar jcf freeradius-client-1.1.tar.bz2 freeradius-client-1.1

#
#  Sign the archive.
#

#
#  These next steps presume you have an account on the main
#  FreeRADIUS web server.
#
scp freeradius-client-1.1.tar.bz2 ...freeradius.org

# move the archive to ftp 'pub/radius' directory

# move the previous version to the 'old' directory
mv freeradius-client-1.0.tar.bz2 old

#
#  delete the old soft link.
#
rm freeradius-client.tar.bz2

#
#  link the new version to it's simple name
#
ln -s freeradius-1.1.tar.bz2 freeradius.tar.bz2     

# go to the www directory

#
#  Ensure that the source archive on the web is updated.
# cvs update -APd radiusd

# edit index.html, and add in the release notes under 'news'
# edit getting.html, and update notes about current/old releases.

# on your work machine again,
rm -rf freeradius-client-1.1.tar.gz freeradius-client-1.1

# go to your working directory
# edit configure.in, to bump the version to '1.2-pre'
autoconf
cvs commit configure configure.in

cd doc

#
#  Add in notes about next release, in preparation for more change log notes.
#
vi ChangeLog
cvs commit ChangeLog