An alternative to using PQM

[Andrew Bennetts]

On Thu, Oct 26, 2006 at 10:43:53AM +0200, Nicholas Allen wrote:
> Hi,
> 
> I just had an idea that could solve our workflow problems if we were to 
> switch to bzr. I'm not really convinced on the idea of using the  PQM 
> and I think this idea would be simpler but offer the same functionality.
> 
> We would write a program, say the "ChangeIntegrator", that would be the 
> only one able to push to the official trunk. The ChangeIntegrator would 
[...]

This sounds like a straightforward variation of the PQM idea.  The difference is
that rather than requesting a merge to trunk via a GPG-signed email to PQM, you
do it by pushing to a special location.  Essentially it's the same idea though,
and if this arrangement is more convenient for you then go for it!

> The ChangeIntegrator would not be a complex program and would not 
> require much to set it up. If we were to write this would it make more 
> sense to do so in Python using bzrlib or would it be easy enough to 
> write as a shell script?

Either way would be fairly easy, I think.  I'd probably write it in Python with
bzrlib personally, because I'm reasonably familiar with bzrlib and so it'd give
me more flexibility, and it's easier to write unit tests for python code than
shell scripts.

If I didn't use bzrlib, I probably wouldn't choose a shell script, I'd write
Python using the subprocess module instead :)

-Andrew.