dev/making-a-release
branchdebian
changeset 325 ed581082bb66
parent 324 36400dcefb67
child 331 aeafdd709c02
equal deleted inserted replaced
321:f4696be23ebf 325:ed581082bb66
       
     1 These are more notes for myself than for anyone else's benefit, but
       
     2 I can never remember what all the steps are, so noting them here.
       
     3 
       
     4 Source changes:
       
     5 
       
     6 - Add stanza to NEWS file
       
     7 - Ensure setup.py version number is bumped
       
     8 - Fix the actual problems (updating NEWS and/or CREDITS as we go)
       
     9 - Test with dev/chroot-test/run-test
       
    10 - Ensure year in README is up to date
       
    11 - Switch to debian
       
    12 - Merge in default
       
    13 - Update Standards-Version
       
    14 - dev/debian-build/dbuild
       
    15 - dev/chroot-test/run-test
       
    16 - When all is well, tag default and debian
       
    17 - dev/debian-build/dbuild_release
       
    18 - dev/chroot-test/run-test
       
    19 
       
    20 Post source changes:
       
    21 
       
    22 - "hg push; hg push public" (also during development)
       
    23 - Mail files in build/debian to Debian sponsor
       
    24 - Copy orig tarball into
       
    25   ~/hg/lshift-web-personal/personal/paul/mercurial-server/
       
    26 - Pull, update, add, push for lshift-web-personal
       
    27 - Update ~/hg/lshift-web/site/mercurial-server.xml
       
    28 - Push
       
    29 - Test that web page works.
       
    30 - Make a blog post
       
    31 - Post to the mercurial mailing list