Merge lp:~ian-clatworthy/bzr/releasing-doc-fix into lp:bzr/2.0

Proposed by Ian Clatworthy
Status: Merged
Approved by: John A Meinel
Approved revision: no longer in the source branch.
Merged at revision: not available
Proposed branch: lp:~ian-clatworthy/bzr/releasing-doc-fix
Merge into: lp:bzr/2.0
Diff against target: 21 lines
1 file modified
doc/developers/releasing.txt (+8/-3)
To merge this branch: bzr merge lp:~ian-clatworthy/bzr/releasing-doc-fix
Reviewer Review Type Date Requested Status
John A Meinel Approve
Review via email: mp+12903@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

The "Releasing Bazaar" process has some minor adjustments now that the new website is rolled out. This patch explains how to edit the new website and points the Release Manager to the SourceDownloads wiki page as the place to register the tar.gz, not the top-level Download page.

Revision history for this message
John A Meinel (jameinel) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Clatworthy wrote:
> Ian Clatworthy has proposed merging lp:~ian-clatworthy/bzr/releasing-doc-fix into lp:bzr/2.0.
>
> Requested reviews:
> bzr-core (bzr-core)
>
>
> The "Releasing Bazaar" process has some minor adjustments now that the new website is rolled out. This patch explains how to edit the new website and points the Release Manager to the SourceDownloads wiki page as the place to register the tar.gz, not the top-level Download page.
>

Looking at:
  http://bazaar-vcs.org/SourceDownloads

It doesn't seem to be a particularly useful page. It seems to have 5
major headings, separating 5 lines of actual content.

I understand the desire to split things up to not be overwhelming, but
this seems to be a bit too far on the other side. (Sort of like reading
an online article where they split it up over 20 pages to get more
advertising hits.)

So this particular patch is:

 review: approve
 merge: approve

Because as it stands, that is what you need to do for a release.

But I'm wondering if it wouldn't be more useful to move the tarball
links onto the bottom of the main Downloads page, rather than waste a
full page for only 5 lines of content...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrLYHsACgkQJdeBCYSNAANMgQCeNyWfiDtTo+FVPIEOtfwBR9lb
RE8AnRzxWdt47EORvvJmz3ESeHne2OnT
=9w9w
-----END PGP SIGNATURE-----

review: Approve
Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

> Looking at:
> http://bazaar-vcs.org/SourceDownloads
>
> It doesn't seem to be a particularly useful page. It seems to have 5
> major headings, separating 5 lines of actual content.
>
> I understand the desire to split things up to not be overwhelming, but
> this seems to be a bit too far on the other side.

> But I'm wondering if it wouldn't be more useful to move the tarball
> links onto the bottom of the main Downloads page, rather than waste a
> full page for only 5 lines of content...

I feel keeping the page is the right choice. It can certainly be improved though. For example, it will get slightly more complex when we start adding in test releases, nightly tarballs, etc.

It would also be more useful if the installation instructions were inline rather than off on a separate page? I'm not sure how much redundancy exists between InstallingFaq and the INSTALL file but it feels weird having the material maintained in multiple places.

Revision history for this message
Martin Pool (mbp) wrote :

2009/10/7 Ian Clatworthy <email address hidden>:
>> Looking at:
>>   http://bazaar-vcs.org/SourceDownloads
>>
>> It doesn't seem to be a particularly useful page. It seems to have 5
>> major headings, separating 5 lines of actual content.
>>
>> I understand the desire to split things up to not be overwhelming, but
>> this seems to be a bit too far on the other side.
>
>> But I'm wondering if it wouldn't be more useful to move the tarball
>> links onto the bottom of the main Downloads page, rather than waste a
>> full page for only 5 lines of content...

I think John has a point here; also that page has no link up to any
larger context. (Actually you can click the 'Download' button but the
page content itself looks a bit fragmented.)

I'd rather get the release manager away from needing to update the
wiki at all: perhaps this page should just point to the Launchpad
download page, and to the instructions. Someone capable of using the
source tarball is probably capable of dealing with that.
--
Martin <http://launchpad.net/~mbp/>

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/developers/releasing.txt'
2--- doc/developers/releasing.txt 2009-09-09 12:57:43 +0000
3+++ doc/developers/releasing.txt 2009-10-06 06:55:24 +0000
4@@ -201,9 +201,14 @@
5 signature. Or, if you prefer, use the
6 ``tools/packaging/lp-upload-release`` script to do this.
7
8-#. Link from http://bazaar-vcs.org/Download to the tarball and signature.
9-
10-#. Announce on the `Bazaar home page <http://bazaar-vcs.org/>`_.
11+#. Link from http://bazaar-vcs.org/SourceDownloads to the tarball and
12+ signature.
13+
14+#. Announce on the `Bazaar website <http://bazaar-vcs.org/>`_.
15+ This page is edited via the lp:bzr-website branch. (Changes
16+ pushed to this branch are refreshed by a cron job on escudero.)
17+
18+#. Announce on the `Bazaar wiki <http://bazaar-vcs.org/Welcome>`_.
19
20 #. Check that the documentation for this release is available in
21 <http://doc.bazaar-vcs.org>. It should be automatically build when the

Subscribers

People subscribed via source and target branches