← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/releasing.txt

  • Committer: John Arbash Meinel
  • Date: 2009-10-14 20:02:28 UTC
  • mfrom: (4634.52.19 2.0.1)
  • mto: (4734.3.1 2.1.0b1)
  • mto: This revision was merged to the branch mainline in revision 4747.
  • Revision ID: john@arbash-meinel.com-20091014200228-fpgssl16h6fmkqww
Merge in the bzr 2.0.1 branch, and resolve a bunch of issues with NEWS.

This also brings in the bug fixes, etc from 2.0.1 that were landed in bzr.dev
after the cut point for 2.1.0b1.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/releasing.txt
212
212
we have a releasable product.  The next step is to make it generally
213
213
available to the world.
214
214
 
215
 
#. Link from http://bazaar-vcs.org/Download to the tarball and signature.
216
 
 
217
 
#. Announce on the `Bazaar home page <http://bazaar-vcs.org/>`_.
 
215
go to the release
 
216
 
 
217
#. Within that release, upload the source tarball and zipfile and the GPG
 
218
   signature.  Or, if you prefer, use the
 
219
   ``tools/packaging/lp-upload-release`` script to do this.
 
220
 
 
221
#. Link from http://bazaar-vcs.org/SourceDownloads to the tarball and
 
222
   signature.
 
223
 
 
224
#. Announce on the `Bazaar website <http://bazaar-vcs.org/>`_.
 
225
   This page is edited via the lp:bzr-website branch. (Changes
 
226
   pushed to this branch are refreshed by a cron job on escudero.)
 
227
 
 
228
#. Announce on the `Bazaar wiki <http://bazaar-vcs.org/Welcome>`_.
218
229
 
219
230
#. Check that the documentation for this release is available in
220
231
   <http://doc.bazaar-vcs.org>.  It should be automatically build when the