Changeset f536399


Ignore:
Timestamp:
May 8, 2010, 12:25:55 PM (10 years ago)
Author:
Nelson Elhage <nelhage@mit.edu>
Branches:
master, release-1.7, release-1.8, release-1.9
Children:
5f08dbe
Parents:
c62c755
git-author:
Nelson Elhage <nelhage@mit.edu> (05/08/10 12:21:08)
git-committer:
Nelson Elhage <nelhage@mit.edu> (05/08/10 12:25:55)
Message:
Update releasing-barnowl for the actual release.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/releasing-barnowl.txt

    r1ea0249 rf536399  
    2222    changelog), makes a tarball
    2323
    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.
     24[ ] Do a locker build (See DOING A LOCKER BUILD)
    2925
    30  [ ] Do two athena9 builds: solaris and linux, usually use multics (or
    31      sun.dialup) for the solaris build, oliver for linux athena9
     26[ ] Update configure.ac on master to bump the version to 1.(N+1)dev
    3227
    33   [ ] Remember to add gnu; add barnowl
     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
    3432
    35   [ ] eval `barnowl-perl-config` to include the perl modules in the
    36       barnowl locker
     33[ ] Copy tarball into /mit/barnowl/web_scripts/dist
    3734
    38   [ ] Run scripts/locker-build TARBALL (barnowl-build-all loops over
    39       all of them in schroots). It overrides existing one.
     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.
    4079
    4180[ ] Sanity-check the builds
     
    4685
    4786[ ] Update symlinks with locker-update script;
     87      locker-update [-b] [-n] VERSION
     88    e.g. locker-update -b -n barnowl-1.6rc1
    4889
    49       locker-update [-b] [-n] VERSION
     90 [ ] Use -b to update the barnowl-beta name
    5091
    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
     92 [ ] Use -n first for dry-run
    6493
    6594
Note: See TracChangeset for help on using the changeset viewer.