[patch] add release notes to news

[John A Meinel]

Martin Pool wrote:
> This patch is meant to summarize the most-important things people need
> to know when upgrading to 0.8.  Many other details are already covered
> in point form.  Is there anything else that should be added/corrected?
> 
> 
> 
> ------------------------------------------------------------------------
> 
> === modified file 'a/NEWS'
> --- a/NEWS	
> +++ b/NEWS	
> @@ -1,4 +1,39 @@
> -bzr 0.8rc1  2006-04-14
> +bzr 0.8rc2  2006-05-05
> +
> +  NOTES WHEN UPGRADING:
> +
> +    Release 0.8 of bzr introduces a new format for history storage, called
> +    'knit', as an evolution of to the 'weave' format used in 0.7.  Local 
> +    and remote operations are faster using weaves than knits.  Several
> +    operations including 'init', 'init-repo', and 'upgrade' take a 
> +    --format option that controls this.  Branching from an existing branch
> +    will keep the same format.

Well, I'm guessing you want to say that :
 Local and remote operations are faster using knits than weaves.

Because otherwise why are we switching?

> +
> +    It is possible to merge, pull and push between branches of different
> +    formats but this is slower than moving data between homogenous
> +    branches.  It is therefore recommended (but not required) that you
> +    upgrade all branches for a project at the same time.  Information on
> +    formats is shown by 'bzr info'.

While this is true, 'bzr info' shows a lot of detail for someone who
just wants to know whether they are a knit or a weave branch.

> +
> +    bzr 0.8 now allows creation of 'repositories', which hold the history 
> +    of files and revisions for several branches.  Previously bzr kept all
> +    the history for a branch within the .bzr directory at the root of the
> +    branch, and this is still the default.  To create a repository, use
> +    the new 'bzr init-repo' command.  Branches exist as directories under
> +    the repository and contain just a small amount of information
> +    indicating the current revision of the branch.
> +
> +    bzr 0.8 also supports 'checkouts', which are similar to in cvs and
> +    subversion.  Checkouts are associated with a branch (optionally in a
> +    repository), which contains all the historical information.  The
> +    result is that a checkout can be deleted without losing any
> +    already-committed revisions.
> +
> +    Repositories and checkouts are not supported with the 0.7 storage
> +    format.  To use them you must upgrad to either knits, or to the
> +    'metaweave' format, which uses weaves but changes the .bzr directory
> +    arrangement.
> +    
>  

Seems good to me. I don't know if you want to mention anything about
light versus plain checkouts. And how plain checkouts would still let
you commit locally when offline.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060505/436a01fd/attachment.pgp