Chris,
I was wondering if there might be some time on the agenda to talk
briefly about assigning issues. Since I'm the stickee for the admin
subcomponent (all created issues get assigned to me by default), I'd
like to get an understanding of how I can go about determining who will
work on specific issues. Clearly, if issues are related to features that
we are currently working on, I can use the various admin subprojects to
figure out who to assign the issue to. But if a bug is found in some
random admin-related file, and the person that last touched that file is
no longer on the project, I need to determine someone to assign the bug
too.
Also, there is a huge backlog of issues that were assigned to Kedar (99
issues). I've been working on getting these reassigned, but am at a loss
on many of them about who to assign the issue to.
A solution for this might be to have an updated page for the admin team
that indicate who is responsible for what module.
Thanks.
Tom
On 5/25/2010 3:36 PM, Chris Kasso wrote:
> The focus today is Console and REST API.
>
> 3:00PM PDT
>
> US toll free: 866-682-4770
> Access code: 5632312
> Security code: 1111
> (*6 to mute/#6 to unmute)
>
> Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>
--
Oracle <http://www.oracle.com>
Tom Mueller | Principal Member of Technical Staff
Phone: +1 4029169943 | Fax: +1 4029169943 | Mobile: +1 4027206872
21915 Hillandale Dr | Elkhorn, NE 68022
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment