|
Size: 1058
Comment: mention im.b.o/t.b.o
|
← Revision 6 as of 2017-02-04 15:09:58 ⇥
Size: 1790
Comment: MORE DETAILS
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Code (for dx) | Changelogs to write: |
| Line 5: | Line 5: |
| * ./bitlbee.h, {{{#define BITLBEE_VERSION "3.2.2"}}}, {{{#define BITLBEE_VERSION_CODE BITLBEE_VER(3, 2, 2)}}} | * Full for ./doc/CHANGES * Mid rich text for website/maint/news.txt (important things) * Small for ./doc/user-guide/misc.xml (strictly only user visible changes) * Tiny for twitter (focus on twitter things) Prepare code/changelogs * ./bitlbee.h, {{{#define BITLBEE_VERSION "3.x.y"}}}, {{{#define BITLBEE_VERSION_CODE BITLBEE_VER(3, x, y)}}} |
| Line 7: | Line 14: |
| * ./doc/user-guide/misc.xml, {{{<sect1 id="whatsnew030202">...</sect1>}}} | * ./doc/user-guide/misc.xml, {{{<sect1 id="whatsnew030x0y">...</sect1>}}} |
| Line 9: | Line 16: |
| Website (for dx) | Prepare website |
| Line 11: | Line 18: |
| * ./bitlbee.data * ./html/changelog.html * ./maint/news.txt |
* `./maint/genchangelog.sh < ../../bitlbee/doc/CHANGES > html/changelog.html` * ./maint/news.txt * `make` (for news.txt) * `make` bitlbee.data |
| Line 15: | Line 23: |
| Timestamps to update when the release actually happens (for wilmer) | Timestamps to update when the release actually happens |
| Line 18: | Line 26: |
| * website: ./bitlbee.data (`$stable_released = '2016-01-01';`) * website: ./html/changelog.html (`<p>Finished ... 200XX</p>`, regen with pandoc or just edit that line) |
* website: `genchangelog.sh` * website: `make bitlbee.data` |
| Line 22: | Line 30: |
| Actually releasing it (for wilmer) | Actually releasing it |
| Line 24: | Line 32: |
| * `git checkout master`, `git merge release-XXX` * `git tag` |
* `git checkout master` * `git merge release-XXX` (maybe) * `git tag 3.x.y` * `make doc` |
| Line 27: | Line 37: |
| * Upload to website * Merge website |
* Verify tarball (see below) * scp bitlbee-3.x.y.tar.gz bitlbee.org: * `bzr push` * From server: `bzr up` * Check staging site * From server: move tarball from scp location to get.bitlbee.org * From server: `make sync` Verify tarball contents: * Get previous release or `wget get.bitlbee.org/src/bitlbee-3.x.x.tar.gz` * Extract both * `diff -Naur bitlbee-3.x.y bitlbee-3.x.z | diffstat` |
| Line 37: | Line 58: |
| * tell rsc or mcepl * flag arch linux as outdated if it hasn't happened magically * update bitlbee-libpurple aur package |
Release Checklist
Changelogs to write:
- Full for ./doc/CHANGES
- Mid rich text for website/maint/news.txt (important things)
- Small for ./doc/user-guide/misc.xml (strictly only user visible changes)
- Tiny for twitter (focus on twitter things)
Prepare code/changelogs
./bitlbee.h, #define BITLBEE_VERSION "3.x.y", #define BITLBEE_VERSION_CODE BITLBEE_VER(3, x, y)
- ./doc/CHANGES
./doc/user-guide/misc.xml, <sect1 id="whatsnew030x0y">...</sect1>
Prepare website
./maint/genchangelog.sh < ../../bitlbee/doc/CHANGES > html/changelog.html
- ./maint/news.txt
make (for news.txt)
make bitlbee.data
Timestamps to update when the release actually happens
code: ./doc/CHANGES (Finished ... 200XX)
website: genchangelog.sh
website: make bitlbee.data
website: ./maint/news.txt (Tue, 02 Jan 2015 13:37:00 +0000, i got the year wrong)
Actually releasing it
git checkout master
git merge release-XXX (maybe)
git tag 3.x.y
make doc
make tar
- Verify tarball (see below)
- scp bitlbee-3.x.y.tar.gz bitlbee.org:
bzr push
From server: bzr up
- Check staging site
- From server: move tarball from scp location to get.bitlbee.org
From server: make sync
Verify tarball contents:
Get previous release or wget get.bitlbee.org/src/bitlbee-3.x.x.tar.gz
- Extract both
diff -Naur bitlbee-3.x.y bitlbee-3.x.z | diffstat
Other stuff:
- announce on twitter
- update channel topic
- build debian packages
- announce abi/api breakages if any
- update im.bitlbee.org and testing.bitlbee.org
- tell rsc or mcepl
- flag arch linux as outdated if it hasn't happened magically
- update bitlbee-libpurple aur package