Urgent: We need to some JIRA housekeeping

[Sean Schofield <se...@gmail.com>]

IMO the JIRA database is getting a little out of hand.  We have over
100 open issues.  I am sure there are some duplicates and some issues
reported that will ultimately be resolved as WON'T FIX but its getting
to be a large list.

There are several issues where users have been kind enough to supply
patches.  Can we resolve to each take a few bugs on and get them
resolved?  It would be helpful if people assigned the bugs to
themselves so we know who is working on what.  Also if you start
looking into a bug it would help to mark "in progress."

For my part I will try to revist the existing tree2 bugs.  It would be
helpfulf if people who knew a component the best fixed the bugs
related to those components.  Its much slower going for those who are
not familiar with the code (esp. to make sure the patch doesn't break
things.)

We should also be looking at who is supply the patches and providing
the help to get these issues resolved.  Ultimately we may want to
consider nominating a few more committers to help out.

sean

Re: Urgent: We need to some JIRA housekeeping

[Martin Marinschek <ma...@gmail.com>]

I would love to help with my components if I get around to do that in
the next few days. I will see what I can do; I wanted to do a revisit
of them anyways at some undefined time ;)

Thanks Sean, by the way, for your enduring and persistent work to make
MyFaces run along the right tracks - it is really great to have a team
member like you aboard!!

regards,

Martin

2005/5/18, Sean Schofield <se...@gmail.com>:
> IMO the JIRA database is getting a little out of hand.  We have over
> 100 open issues.  I am sure there are some duplicates and some issues
> reported that will ultimately be resolved as WON'T FIX but its getting
> to be a large list.
> 
> There are several issues where users have been kind enough to supply
> patches.  Can we resolve to each take a few bugs on and get them
> resolved?  It would be helpful if people assigned the bugs to
> themselves so we know who is working on what.  Also if you start
> looking into a bug it would help to mark "in progress."
> 
> For my part I will try to revist the existing tree2 bugs.  It would be
> helpfulf if people who knew a component the best fixed the bugs
> related to those components.  Its much slower going for those who are
> not familiar with the code (esp. to make sure the patch doesn't break
> things.)
> 
> We should also be looking at who is supply the patches and providing
> the help to get these issues resolved.  Ultimately we may want to
> consider nominating a few more committers to help out.
> 
> sean
>