Re: Weird triage and sharing bugs to focus on

Okay, I think of the 5 bugs below, 1 and 3 are the most serious. I've  
moved to the top 'Emergency' section on the bug prioritization list:  
http://chandlerproject.org/Notes/OneDotZeroDesktopBugs

Jeffrey can you take a look at #2 and make sure we're all talking  
about the same bug?

Thanks, more in-line.

Mimi

On Oct 5, 2007, at 3:18 PM, Morgen Sagen wrote:

>> 1. 'from' EIM field is causing items to be marked as edited/ in  
>> conflict
>> that aren't really (at least not in a way the user can see)
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=10799
>
> I see this is targetted at 0.7.future -- should it be 0.7.2?

Untargetted and recommended for 0.7.2

>
>> 2. Reload bug that screws up triage status when people dump/reload  
>> shared
>> collections. Bug#?
>
> There was a bug where the (incorrect) order of items being exported
> was causing problems during subsequent reloads, but over time this
> should go away as people move to the new code.

Just want to make sure you and I are talking about same bug. Jeffrey  
has been referring to this as the 'reload' bug. Jeffrey, is the bug  
Morgen describing the same bug we've been talking about?

>
>> 3. Entire series pops into NOW all the
>> time: https://bugzilla.osafoundation.org/show_bug.cgi?id=10948
>
> I spent a bunch of time on this one yesterday (oh, and I see it's
> actually an untargetted bug), and it seems that we just need to ignore
> the doAutoTriageOnDateChange value when deciding to mark an item
> unread.  This is already part of bug 10799.
>
>> 4. I unstamped a recurring series. And then after I synced, it re- 
>> appeared
>> at the top of NOW as unread and had re-stamped itself. But I was  
>> still list
>> as the last person to edit it. Now if I try to stamp it again, I  
>> can't get
>> anything to stick in the To:
>> field. https://bugzilla.osafoundation.org/show_bug.cgi?id=10980

Uploaded

>
> That one sounds fun.  I would definitely upload a repo for that bug.
>
>> 5. Sharing bug: I delete an item on a shared collection. I sync,  
>> it comes
>> back. (Is there a bug for this already?)
>
> Well, when this happens it means there are inbound changes for the
> item, so we bring the item back.  So we need to figure out why the
> server is sending you changes.  Please file a bug with repo and logs.

Filed and uploaded.

>
> ~morgen
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design