[zope2-tracker] [Bug 143593] Re: ConflictErrors cause "Shouldn't load state for?"

ChrisW chris at simplistix.co.uk
Mon Apr 12 03:20:33 EDT 2010


Tres Seaver wrote:
> The "triaged" state used by some projects on Launchpad is probably the
> right fit, especially if we add a "weird-keep-for-future-reference" tag
> as well.

Good, lets got for that. Hopefully this issue can get into that state 
before the gods of launchpad eat it ;-)

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk

-- 
ConflictErrors cause "Shouldn't load state for?"
https://bugs.launchpad.net/bugs/143593
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.


More information about the zope2-tracker mailing list