[rfc] news layout tweak (was Re: bzr 1.13 release manager wanted)

[John Arbash Meinel]

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

Matt Nordhoff wrote:
> Martin Pool wrote:
>> 2009/3/6 Martin Pool <mbp at sourcefrog.net>:
>>>> Do I just pester developers for this information or do I get the privledge
>>>> of scanning the logs for this info myself. :-)
>>> It should all be in NEWS in the tree ready to go.  You just need to
>>> add the date and header, and write a one-or-two paragraph summary of
>>> them.
>> Oh, I'd like to pass on one suggestion from Karl Fogel for a change in
>> the NEWS file.  (I meant to write up a releasing.txt patch but haven't
>> got to it yet.)  And that is: many people just upgrade between the
>> final releases and the current layout with major headings for each rc
>> arguably obscures what changed from 1.12final to 1.13final.  So, Karl
>> suggests, we should have just one heading and mark the few things that
>> changed after rc1 with "changed after rc1" or "changed in 1.13final"
>> or similar.  Any comments?
> 
> I've always liked being able to easily see what changed in each release
> candidate and the final release, and I imagine users who run release
> candidates would agree.
> 
> On the other hand, I run bzr.dev, and maybe I just hate change. :-P
> 
> -0.5 from me, but if you want to make the change, I wouldn't fight it.

Running bzr.dev and you hate change? :)

What if we just put them at the top, in a 'changed since rc1', but
without a major heading.

So right now we have:

bzr 1.12 "1234567890" 2009-02-13
- --------------------------------

This release of Bazaar contains many improvements to the speed,
documentation and functionality of ``bzr log`` and the display of logged
revisions by ``bzr status``.  bzr now also gives a better indication of
progress, both in the way operations are drawn onto a text terminal, and
by showing the rate of network IO.

  BUG FIXES:

    * ``bzr init --development-wt5[-rich-root]`` would fail because of
      circular import errors. (John Arbash Meinel, #328135)

  DOCUMENTATION:

    * Expanded the help for log and added a new help topic called
      ``log-formats``.  (Ian Clatworthy)


bzr 1.12rc1 "1234567890" 2009-02-10
- -----------------------------------

  COMPATIBILITY BREAKS:
...


And what if we changed that to:


bzr 1.12 "1234567890" 2009-02-13
- --------------------------------

This release of Bazaar contains many improvements to the speed,
documentation and functionality of ``bzr log`` and the display of logged
revisions by ``bzr status``.  bzr now also gives a better indication of
progress, both in the way operations are drawn onto a text terminal, and
by showing the rate of network IO.

  CHANGES FROM bzr 1.12rc1 2009-02-10:

    * ``bzr init --development-wt5[-rich-root]`` would fail because of
      circular import errors. (John Arbash Meinel, #328135)

    * Expanded the help for log and added a new help topic called
      ``log-formats``.  (Ian Clatworthy)

  COMPATIBILITY BREAKS:


That would still make the rc1 versus final changes clear, while not
making it seem like an entirely different category.

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

iEYEARECAAYFAkmxMVQACgkQJdeBCYSNAAPwmwCgq10/AsREiAO0xAN0U07YU3O2
5PgAn3+h2IcNI4M3JeIg9mprX0DUVXD8
=DJBL
-----END PGP SIGNATURE-----