1 | -*- mode: org *- |
---|
2 | * DOING A BARNOWL RELEASE |
---|
3 | - [ ] Send mail to barnowl-dev indicating that a release is |
---|
4 | happening soon, and soliciting any improvements that |
---|
5 | developers want included in the release. |
---|
6 | - [ ] Wait a while (a week or so, or more if necessary) for any |
---|
7 | pending patches to get in. |
---|
8 | - [ ] Prepare the -rc commit |
---|
9 | - [ ] Run ./scripts/add-changelog NEW-VERSION PREV-TAG..HEAD |
---|
10 | - [ ] Edit ChangeLog to combine and filter entries |
---|
11 | - [ ] Edit configure.ac to bump the version to 1.Nrc1 |
---|
12 | - [ ] Commit with message 'BarnOwl 1.Nrc1'; don't push until after |
---|
13 | builds all succeed |
---|
14 | - [ ] Run scripts/do-release with -f (so it won't complain about |
---|
15 | missing changelog), makes a tarball |
---|
16 | - [ ] Do a locker build (See DOING A LOCKER BUILD) |
---|
17 | - [ ] Update configure.ac on master to bump the version to 1.(N+1)dev |
---|
18 | - [ ] Add the barnowl-1.(N+1)dev git tag |
---|
19 | - [ ] Push git git: |
---|
20 | - [ ] The RC commit |
---|
21 | - [ ] The configure.ac change on master |
---|
22 | - [ ] A release-1.N branch pointing at the RC commit |
---|
23 | - [ ] the new git tags |
---|
24 | - [ ] Update debian/changelog on the launchpad build using `dch -v 1.(N+1)` |
---|
25 | - [ ] bzr branch lp:~barnowl/barnowl/packaging && cd packaging && dch -v 1.(N+1) |
---|
26 | - [ ] Add relevant changelog entries such as "New upstream release" or |
---|
27 | "Placeholder version number for daily builds."; fix your name and email |
---|
28 | if necessary |
---|
29 | - [ ] bzr commit && bzr push |
---|
30 | - [ ] Copy tarball into /mit/barnowl/web_scripts/dist |
---|
31 | - [ ] Send mail announcing the RC to barnowl-dev@mit.edu |
---|
32 | - [ ] Wait 1-2 weeks, collect any bug reports |
---|
33 | - [ ] Fix any reported bugs on master |
---|
34 | - [ ] Cherry-pick/backport appropriate fixes from master onto |
---|
35 | release-1.N |
---|
36 | - [ ] If there have been many or large bugfixes, repeat the process |
---|
37 | for barnowl 1.Nrc2 |
---|
38 | |
---|
39 | * DOING THE ACTUAL RELEASE |
---|
40 | - [ ] Update the changelog and configure.ac for barnowl 1.N |
---|
41 | - [ ] Copy the changelog changes to the master branch |
---|
42 | - [ ] run ./scripts/do-release |
---|
43 | - [ ] Do the locker build |
---|
44 | - [ ] Push the release tag |
---|
45 | - [ ] Write up release notes |
---|
46 | (I usually use the previous release's email as a template) |
---|
47 | - [ ] Update the website |
---|
48 | - [ ] Add the line that `do-release` printed to the changelog on the home page |
---|
49 | - [ ] Add your release notes as /release-notes/1.N |
---|
50 | - [ ] Send the release notes to barnowl-users@mit.edu |
---|
51 | |
---|
52 | * DOING A LOCKER BUILD |
---|
53 | - [ ] Copy the tarball to build@nelhage.com |
---|
54 | - [ ] ssh to build@nelhage.com and kinit |
---|
55 | - [ ] On build@nelhage.com, run barnowl-build-all TARBALL. |
---|
56 | This script does builds for all Debathena platforms using chroots |
---|
57 | on nelhage.com, and ssh's to Athena 9 machines to do the two |
---|
58 | Athena 9 builds. |
---|
59 | - [ ] Sanity-check the builds |
---|
60 | - [ ] Do cursory testing on debathena platforms and both athena9s. |
---|
61 | - [ ] chroots on nelhage.com also useful |
---|
62 | - [ ] Update symlinks with locker-update script; |
---|
63 | - locker-update [-b] [-n] VERSION |
---|
64 | - e.g. locker-update -b -n barnowl-1.6rc1 |
---|
65 | - [ ] Use -b to update the barnowl-beta name |
---|
66 | - [ ] Use -n first for dry-run |
---|
67 | |
---|
68 | * LOCKER LAYOUT |
---|
69 | - builds/barnowl-VERSION contains the arch-independent files by |
---|
70 | version |
---|
71 | - arch/SYSNAME/bin/barnowl-VERSION is the actual binary |
---|
72 | - arch/SYSNAME/bin/barnowl is a symlink to ../../common/bin/barnowl |
---|
73 | (wrapper script runs barnowl.real). .../barnowl.real is a symlink |
---|
74 | to the latest version. |
---|
75 | - zcrypt is also installed with a versioned name, but currently |
---|
76 | barnowl-N will not run zcrypt-N, so we can't change that interface |
---|
77 | at all. |
---|