source: doc/releasing-barnowl.txt @ f536399

release-1.7release-1.8release-1.9
Last change on this file since f536399 was f536399, checked in by Nelson Elhage <nelhage@mit.edu>, 11 years ago
Update releasing-barnowl for the actual release.
  • Property mode set to 100644
File size: 2.8 KB
Line 
1DOING A BARNOWL RELEASE
2
3[ ] Send mail to barnowl-dev indicating that a release is happening
4    soon, and soliciting any improvements that developers want
5    included in the release.
6
7[ ] Wait a while (a week or so, or more if necessary) for any pending
8    patches to get in.
9
10[ ] Prepare the -rc commit
11
12 [ ] Run ./scripts/add-changelog NEW-VERSION PREV-TAG..HEAD
13
14 [ ] Edit ChangeLog to combine and filter entries
15
16 [ ] Edit configure.ac to bump the version to 1.Nrc1
17
18[ ] Commit with message 'BarnOwl 1.Nrc1'; don't push until after
19    builds all succeed
20
21[ ] Run scripts/do-release with -f (so it won't complain about missing
22    changelog), makes a tarball
23
24[ ] Do a locker build (See DOING A LOCKER BUILD)
25
26[ ] Update configure.ac on master to bump the version to 1.(N+1)dev
27
28[ ] Push git git:
29 [ ] The RC commit
30 [ ] The configure.ac change on master
31 [ ] A release-1.N branch pointing at the RC commit
32
33[ ] Copy tarball into /mit/barnowl/web_scripts/dist
34
35[ ] Send mail announcing the RC to barnowl-dev@mit.edu
36
37[ ] Wait 1-2 weeks, collect any bug reports
38
39[ ] Fix any reported bugs on master
40
41[ ] Cherry-pick/backport appropriate fixes from master onto
42    release-1.N
43
44[ ] If there have been many or large bugfixes, repeat the process for
45    barnowl 1.Nrc2
46
47DOING THE ACTUAL RELEASE
48
49[ ] Update the changelog and configure.ac for barnowl 1.N
50
51[ ] run ./scripts/do-release
52
53[ ] Do the locker build
54
55[ ] Push the release tag
56
57[ ] Write up release notes
58    (I usually use the previous release's email as a template)
59
60[ ] Update the website
61
62 [ ] Add the line that `do-release` printed to the changelog on the home page
63
64 [ ] Add your release notes as /release-notes/1.N
65
66[ ] Send the release notes to barnowl-users@mit.edu
67
68
69DOING A LOCKER BUILD
70
71[ ] Copy the tarball to build@nelhage.com
72
73[ ] ssh to build@nelhage.com and kinit
74
75[ ] On build@nelhage.com, run barnowl-build-all TARBALL.
76    This script does builds for all Debathena platforms using chroots
77    on nelhage.com, and ssh's to Athena 9 machines to do the two
78    Athena 9 builds.
79
80[ ] Sanity-check the builds
81
82 [ ] Do cursory testing on debathena platforms and both athena9s.
83
84 [ ] chroots on nelhage.com also useful
85
86[ ] Update symlinks with locker-update script;
87      locker-update [-b] [-n] VERSION
88    e.g. locker-update -b -n barnowl-1.6rc1
89
90 [ ] Use -b to update the barnowl-beta name
91
92 [ ] Use -n first for dry-run
93
94
95LOCKER LAYOUT
96
97* builds/barnowl-VERSION contains the arch-independent files by
98  version
99
100* arch/SYSNAME/bin/barnowl-VERSION is the actual binary
101
102* arch/SYSNAME/bin/barnowl is a symlink to ../../common/bin/barnowl
103  (wrapper script runs barnowl.real). .../barnowl.real is a symlink to
104  the latest version.
105
106* zcrypt is also installed with a versioned name, but currently
107  barnowl-N will not run zcrypt-N, so we can't change that interface
108  at all.
Note: See TracBrowser for help on using the repository browser.