← Back to team overview

launchpad-dev team mailing list archive

Re: Unable to figure out what to do for loggerhead

 

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


...

>> For now, I can certainly be vigilant about running the test suite. It
>> feels funny to have it finish so quickly.
>>
>> Though I'm also not testing against python-2.5, which I would like to
>> preserve compatibility with.
> 
> We could get a pqm or a tarmac configured, for sure. If we just add a
> rule to the existing bzr pqm that probably meets all your needs and
> would be easiest. Would that suffice? We'd need to get a one time sync
> of keys from the lp pqm to get lp folk commit access.
> 
> Alternatively, there *is* a simple tarmac for lp-oops and some other
> things, I'm reasonably sure we can add loggerhead/trunk to that easily
> too; I shall enquire next week when I overlap the relevant folk.
> 
> -Rob
> 

I know Martin said if we set something up, he'd probably rather it was
tarmac. And I'd be interested in experimenting with it.

I'm a bit curious how you trigger it. AIUI, it polls launchpad to see if
there is anything Approved, and if so, merges it, runs the tests, etc.

What is the latency on that polling? Or is it meant to be using PSHB or
some other external notification system?

I also know that in bzr-world I would really miss the distinction
between Approved and "Queued". Or in Bundle Buggy terms, BB:tweak vs
BB:approve. It may not matter as much for loggerhead stuff.

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

iEYEARECAAYFAk1UvMcACgkQJdeBCYSNAAMLYACgyT4VhrTtI6mrg8F7DBVnCCmA
XokAn2Kh94JHZGItZ7MoXj9Y2e4lUzWe
=BBL1
-----END PGP SIGNATURE-----



Follow ups

References