proof-of-concept: plugin for organizing set of bzr branches as complex project

[John Arbash Meinel]

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


...

> If you want to comment my config.prj format please speak up.
> 
> Alexander.
> 
> P.S. If you think I'm doing foolish work -- I'm fine with it, I'm doing
> it for
> my personal usage in first place. So you don't need to tell me this.
> 
> 
> 

This certainly sounds interesting. I'm curious if you looked at
config-manager which at least works in a similar way. (With a possible
advantage that it speaks many different VCSs, so you could have one
directory from SVN and another from BZR, etc.)

I think the reason that most systems version the file is so that you can
get back exact snapshots from the past. (So you can get the exact
configuration for your 1.0 release.) It is possible that versioning
every revision is too often, but I would certainly suggest that you
think about having a way to be very exact about what revision-ids you
want to grab.

There are certainly 2 use cases

1) Give me the latest version of all the branches so I can get started

and

2) Give me an exact snapshot so I can recreate the whole project as it
existed in the past.

Your solution sounds great for (1), and I'm curious if you have thought
much about (2).

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

iEYEARECAAYFAkkm+qcACgkQJdeBCYSNAAODmACdHd7lSemBdWcuTajng8NMhxjP
AWIAnA4JMI8ZBouRnnw3PWuEaYD1+VG7
=CoFW
-----END PGP SIGNATURE-----