0.6.2.

* user double-submitted the same message text to an 
issue
* in the Web interface, I hit Remove on the most recent 
duplicate message in the issue
* the duplicate was removed, but the ordering of the 
existing messages on the issue changed

Before Remove:

msg586, msg843, msg852, msg1743, msg1747, msg1748, 
msg1750, msg1751

After Remove on msg1751:

msg1743, msg1747, msg1748, msg1750, msg586, 
msg843, msg852

Looks almost as if it's doing an alpha, not numeric, sort: 
the shift from 3-digit to 4-digit issue numbers has 
thrown it.

Logged In: YES 
user_id=6405

Yep, it's doing an alpha sort. Currently IDs are stored as Strings (for 
purely historical reasons - the original Roundup spec didn't have a 
Number type). One of these days I'll put in the code required to turn the 
String IDs into Numbers... it's not going to be pretty though :) 
 
 

Logged In: YES 
user_id=6405

IIRC someone's already done some patching to change ids to Numbers 
for the sqlite backend. The biggest concern is that some detector code 
will break - and since I can't update that code during a normal Roundup 
source update, I'll have to include upgrading.txt instructions, and I'm 
trying to avoid that these days :) 
 

Logged In: YES 
user_id=6405

This should be fixed in CVS - though we're still working with non-numeric 
ids :( 
 
Sorry, the fix is too big to back-port :(