FWIW, on extensions, what we have been finding works is to file
separate bugs for each platform's UI implementation. It is just too
much code to track with one bug. You end up with these mega bugs that
never close.

We label each bug OS-<whatever the case may be>

- a

On Wed, Oct 7, 2009 at 10:01 AM, Ben Goodger (Google) <[email protected]> wrote:
>
> Because we have different frontend codebases on different platforms,
> it's important that we strive to maintain feature parity between them.
> For this reason whenever we implement a modification to the UI in
> substance (e.g. add a feature, change a behavior) we should make sure
> to file a bug for the other platforms as well (or implement it there
> if you're capable).
>
> We should probably have some sort of platform parity label in the bug
> tracker so we can track these divergences.
>
> -Ben
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to