New format checklist

[John Arbash Meinel]

I'm trying to put together all of the things which require a new branch
format. So please add on if I have missed anything. Remembering the pain
of the last format upgrade, it would be nice to have a single upgrade,
or perhaps more support for older formats.

1) knits
   These obviously require a new format. I'm not sure what the timeline
   for them being completed is.

2) bound branches
   A new format is not strictly required, but it prevents old clients
   from committing to a bound branch, and not respecting its bound state

3) Encoding revision & file ids
   The final decision seemed to be that we should allow most unicode
   characters in revision and file ids. Which means we need a mapping
   between ids and valid filesystem names.
   I'm not sure how to map unicode into filenames. I know there is
   urlencoding which should handle a lot of the bad characters. But
   does it map from unicode? A lot of filesystems have their own
   encoding (on windows it is UTF-16/mbcs, a lot of other systems use
   utf-8). Do we want to do something like:
      path = urlencode(revision_id.encode('utf-8'))

4) Refactoring of metadata. We would like to split things under .bzr
   into:
	.bzr/checkout/
	.bzr/branch/
	.bzr/repository/
   Which will help ease the transition when we start separating where
   these objects reside.

Anything else?

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060102/a964c691/attachment.pgp