| 1 | DOING 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 | [ ] Make all the builds |
|---|
| 25 | |
|---|
| 26 | [ ] On build@nelhage.com, run barnowl-build-all TARBALL to build for |
|---|
| 27 | everything with chroots, doesn't do athena 9 builds. Builds into |
|---|
| 28 | locker parellel to all other versions. |
|---|
| 29 | |
|---|
| 30 | [ ] Do two athena9 builds: solaris and linux, usually use multics (or |
|---|
| 31 | sun.dialup) for the solaris build, oliver for linux athena9 |
|---|
| 32 | |
|---|
| 33 | [ ] Remember to add gnu; add barnowl |
|---|
| 34 | |
|---|
| 35 | [ ] eval `barnowl-perl-config` to include the perl modules in the |
|---|
| 36 | barnowl locker |
|---|
| 37 | |
|---|
| 38 | [ ] Run scripts/locker-build TARBALL (barnowl-build-all loops over |
|---|
| 39 | all of them in schroots). It overrides existing one. |
|---|
| 40 | |
|---|
| 41 | [ ] Sanity-check the builds |
|---|
| 42 | |
|---|
| 43 | [ ] Do cursory testing on debathena platforms and both athena9s. |
|---|
| 44 | |
|---|
| 45 | [ ] chroots on nelhage.com also useful |
|---|
| 46 | |
|---|
| 47 | [ ] Update symlinks with locker-update script; |
|---|
| 48 | |
|---|
| 49 | locker-update [-b] [-n] VERSION |
|---|
| 50 | |
|---|
| 51 | e.g. locker-update -b -n barnowl-1.6rc1 |
|---|
| 52 | |
|---|
| 53 | [ ] -b for the beta |
|---|
| 54 | |
|---|
| 55 | [ ] -n first for dry-run |
|---|
| 56 | |
|---|
| 57 | [ ] Push the RC commit |
|---|
| 58 | |
|---|
| 59 | [ ] Copy tarball into /mit/barnowl/web_scripts/dist |
|---|
| 60 | |
|---|
| 61 | [ ] Send mail (rcs to barnowl-dev@, release to barnowl-users@) |
|---|
| 62 | |
|---|
| 63 | [ ] Make an actual release about a week after the RC |
|---|
| 64 | |
|---|
| 65 | |
|---|
| 66 | LOCKER LAYOUT |
|---|
| 67 | |
|---|
| 68 | * builds/barnowl-VERSION contains the arch-independent files by |
|---|
| 69 | version |
|---|
| 70 | |
|---|
| 71 | * arch/SYSNAME/bin/barnowl-VERSION is the actual binary |
|---|
| 72 | |
|---|
| 73 | * arch/SYSNAME/bin/barnowl is a symlink to ../../common/bin/barnowl |
|---|
| 74 | (wrapper script runs barnowl.real). .../barnowl.real is a symlink to |
|---|
| 75 | the latest version. |
|---|
| 76 | |
|---|
| 77 | * zcrypt is also installed with a versioned name, but currently |
|---|
| 78 | barnowl-N will not run zcrypt-N, so we can't change that interface |
|---|
| 79 | at all. |
|---|
