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

[Tres Seaver]

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

Lennart Regebro wrote:
> On Thu, Apr 8, 2010 at 10:56, ChrisW <chris at simplistix.co.uk> wrote:
>> Actually, no. This was a hard-to-reproduce error that only occurred
>> under high load.
>>
>> Closing it off will just mean that we start the process again, rather
>> than having this issue open and available as a container for the error
>> reports...
> 
> Can we have a state for "weird errors that can't be reproduced but
> needs to be kept here for future reference"? I can see the use of
> that, so we can keep track of whom it happens too and how often.

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.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvAbpsACgkQ+gerLs4ltQ7xGgCfbXLrtj7EpanfrFMGC4QtQM4O
V5AAn0bWX00z6/2+2wNyMfWe8k2YI9xR
=dnRU
-----END PGP SIGNATURE-----

-- 
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.