[Release] 3.11 liaison change

[Keith Hodges]

>
> A typical use case is that a developer starts some bit of work this
> week and then only gets around to work on it again two weeks later.
> What the developer needs to be able to do is to find out what changed,
> find out whether it affects any part that he was working on, and merge
> eventual differences. Monticello can handle these tasks trivially, I
> have no idea how Mantis or Bob would help me here.
If you specify a build that you are working on then there is an MC
repository for that build, e.g. 3.11. As you modify the items that
contribute to that build the MC repository gets updated each time the
build is run, if a pacakge has changed.

I admit that this is the most experimental and unproven part of the idea.

An example...

1. I run the build... and it generates the packages e.g.
311/Network-bob.20.mcz

2. A while later I have a couple more fixes added to Mantis, Bob tracks
mantis and so can work out what they are.

3. I run the build again and it generates the package
3.11/Network-bob.21.mcz and adds the comment indicating that two fixes
were added since the last time.

like I say experimental (and somewhat slow)

Keith