summaryrefslogtreecommitdiff
path: root/extras/README.releasing
blob: 0943d9821fabbad5b04d282d59fe3c65ed0a5828 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
To make a release:

Pre-release:
* Update src/Core/Banshee.Core/Resources/contributors.xml
* Update AUTHORS (cd extras/ && ./create-authors > ../AUTHORS)
* Update NEWS
* Bump version in configure.ac (don't forget the display version)
* Update banshee.doap, build/windows/Installer*
* Run `make distcheck`
* Commit everything

Release:
* Run the `extras/make-release` script (from extras/ directory)
  + Add --unstable if appropriate
  + Note that this makes the tag, adds the version to bugzilla,
    and uploads the tarballs.

Post-release:
* Update the website
  + Add download/archives/$version page
    - Use `cd extras && ./create-release-notes > foo` script
      + By hand modify 'the previous major release notes...' section
    - Set sort order, parent, and permalink
  + Update Downloads/Archives page, adding entry for this release
  + Add a new blog post, uncategorized, tag 'news'
* For stable releases, ssh banshee@banshee.fm, update web/download.banshee.fm/release-info/banshee
  + This is used by the website to know what the latest release is
* Send announce e-mail
  + To: banshee-list@gnome.org, gnome-announce-list@gnome.org, mono-announce-list@lists.ximian.com