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

[Tres Seaver]

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

ChrisW wrote:
> Tres Seaver wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> ChrisW wrote:
>>> Yes, none of the above were being done in any code we had written...
>>>
>>> Please can you change to a status other than incomplete so that this bug
>>> doesn't become expired?
>> "Incomplete" means "we don't have enough information to reproduce or
>> diagnose the bug", which is pretty accurate AFAICT.
> 
> Yeah, it's just annoying that, on Launchpad, that status also implies 
> 'we will shortly delete your issue'...

We do have ancient-but-incomplete bugs for Zope2:

https://bugs.launchpad.net/zope2/+bugs?field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE


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

iEYEARECAAYFAku7Ss8ACgkQ+gerLs4ltQ7LoQCfZG/jsXL7dMBa3apQ9Mo9vPcd
IPAAnigaztYhWb/YAyZAaFbcg8ApI8/A
=uA69
-----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.