source: doc/releasing-barnowl.txt @ 4ae24dd

Last change on this file since 4ae24dd was 4ae24dd, checked in by Jason Gross <jgross@mit.edu>, 10 years ago
Add instructions for updating launchpad The build version number of the launchpad daily builds should match the current development version number.
  • Property mode set to 100644
File size: 3.4 KB
Line 
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  - [ ] Push git git:
19   - [ ] The RC commit
20   - [ ] The configure.ac change on master
21   - [ ] A release-1.N branch pointing at the RC commit
22  - [ ] Update debian/changelog on the launchpad build using `dch -v 1.(N+1)`
23   - [ ] bzr branch lp:~barnowl/barnowl/packaging && cd packaging && dch -v 1.(N+1)
24   - [ ] Add relevant changelog entries such as "New upstream release" or
25         "Placeholder version number for daily builds."; fix your name and email
26         if necessary
27   - [ ] bzr commit && bzr push
28  - [ ] Copy tarball into /mit/barnowl/web_scripts/dist
29  - [ ] Send mail announcing the RC to barnowl-dev@mit.edu
30  - [ ] Wait 1-2 weeks, collect any bug reports
31  - [ ] Fix any reported bugs on master
32  - [ ] Cherry-pick/backport appropriate fixes from master onto
33        release-1.N
34  - [ ] If there have been many or large bugfixes, repeat the process
35        for barnowl 1.Nrc2
36
37* DOING THE ACTUAL RELEASE
38  - [ ] Update the changelog and configure.ac for barnowl 1.N
39  - [ ] run ./scripts/do-release
40  - [ ] Do the locker build
41  - [ ] Push the release tag
42  - [ ] Write up release notes
43        (I usually use the previous release's email as a template)
44  - [ ] Update the website
45   - [ ] Add the line that `do-release` printed to the changelog on the home page
46   - [ ] Add your release notes as /release-notes/1.N
47  - [ ] Send the release notes to barnowl-users@mit.edu
48
49* DOING A LOCKER BUILD
50  - [ ] Copy the tarball to build@nelhage.com
51  - [ ] ssh to build@nelhage.com and kinit
52  - [ ] On build@nelhage.com, run barnowl-build-all TARBALL.
53        This script does builds for all Debathena platforms using chroots
54        on nelhage.com, and ssh's to Athena 9 machines to do the two
55        Athena 9 builds.
56  - [ ] Sanity-check the builds
57   - [ ] Do cursory testing on debathena platforms and both athena9s.
58   - [ ] chroots on nelhage.com also useful
59  - [ ] Update symlinks with locker-update script;
60        - locker-update [-b] [-n] VERSION
61        - e.g. locker-update -b -n barnowl-1.6rc1
62   - [ ] Use -b to update the barnowl-beta name
63   - [ ] Use -n first for dry-run
64
65* LOCKER LAYOUT
66  - builds/barnowl-VERSION contains the arch-independent files by
67    version
68  - arch/SYSNAME/bin/barnowl-VERSION is the actual binary
69  - arch/SYSNAME/bin/barnowl is a symlink to ../../common/bin/barnowl
70    (wrapper script runs barnowl.real). .../barnowl.real is a symlink
71    to the latest version.
72  - zcrypt is also installed with a versioned name, but currently
73    barnowl-N will not run zcrypt-N, so we can't change that interface
74    at all.
Note: See TracBrowser for help on using the repository browser.