tags

[David Farning]

On Sun, 2007-02-18 at 10:19 -0500, John Vivirito wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> im thinking we could use tags for a few things.
> Tag for upstream either like waiting for upstream or needs to be
> reported upstream.
> Tag for wishlist maybe something like mt-decide or mt-needack. we have
> alot of wishlist bugs that are unconfirmed and i would like to get them
> out of that catagory. im not sure if mt-needsinfo as i set the bug to
> needsinfo because only really Alexander can be the deciding vote on if
> we add it or not.
> 

The flow i am thinking about is that once a bug has all of the necessary
information that it is a legitimate bug.  It should be moved to the
confirmed state.  While in confirmed a number of decisions need to be
made.

Is this an upstream issues? 
  If yes, Which upstream?
      Mozilla.
      Gnome.
    Does on upstream issue report exist?
      If yes, link to upstream issue.
      If No, create a new upstream issue.
  If no(not upstream)
    What type of work needs to be done?
      Localization?
      Simple typo?

Once it has been pushed or accepted locally it will change to in
progress.

This is a basic out line of one way of viewing the flow.  The pushing
upstream will be interesting.  Simply becuase there are 20,000 open
issues in mozilla.  It will take a person experienced with their
bugzilla to do the search and push the issues correctly.

Pushing to gnash will be easy,  Jave they are willing talk.
Adobe....hmmm

Thoughts?

thanks
-- 
David Farning <dfarning at gmail.com>