[Cosmo-dev] Cosmo Task Triage
br at osafoundation.org
Wed Jun 13 17:18:42 PDT 2007
Seems very reasonable to me.
On Jun 13, 2007, at 3:36 PM, Sheila Mooney wrote:
> Ted asked me to go through all the tasks and look at any items we
> think could be deferred from a product perspective in order to help
> us meet our feature freeze date. I have not made any changes to
> bugzilla and simply wanted to provide Ted with this info so he
> could manage the list. In the following wiki page, I have
> highlighted which bugs are puntable as well as a few that are P3s
> but probably a higher priority than the rest of the P3s.
> + All timezone related bugs could be punted since we have as much
> as we need for Preview right now. There was one bug assigned to
> Randy and I wasn't sure whether or not to punt that. It might an
> interop issue but I was going to let Ted decide on this one.
> + There are several other P3s that have to do with alarms or
> dashboard features we aren't going to deal with.
> + There are 4 P3s that we would like to have fixed and could be
> promoted to P2 if that's easier to keep track of them. I am
> assuming that all other P3s might not get done so I wanted to make
> sure these were isolated.
> There is a large number of rebranding task bugs. In my opinion
> these don't block feature freeze. Technically they are new
> functionality but most of it is very isolated and typically we
> simply fixed these in the bug fix stage and not required them to be
> done by feature freeze. This really means that they are needed for
> code complete not feature freeze. Others might feel we need to
> block on this but this is just my 2 cents.
> Let me know if you have any comments, concerns or questions about a
> particular bug. Mimi and primarily went through the UI features and
> skipped over any dev type and infrastructure items.
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev