[etoys-dev] jira re-arrangement

[Timothy Falconer]

On Aug 24, 2009, at 6:39 PM, Yoshiki Ohshima wrote:

>>>> Add a comment saying, "works for me" and then put the change to the
>>>> update stream and click "Closed" (aka Published)
>>>
>>> Hmm, putting the change to the update stream is so far limited to
>>> certain users.  (And "works for me" just by somebody often is not  
>>> the
>>> right reason to "Close" an item.)
>>
>> I think my initial process page said that software team members  
>> verify
>> and push to the stream (#13):
>>
>> http://confluence.immuexa.com/display/sq/Process
>>
>> Priorities and code review are the primary function of the software
>> team.
>>
>> Is this sufficient?
>
>  The text in the "jira re-arrangement" email was written to the
> community, right?
>
>  Surely reviews and reports that say the code works for some
> community member is useful and important, but it shouldn't be
> automatically tied to "Closed" and "Published" status, I thought.
>
> -- Yoshiki

Only software team members can close (publish) an issue (the people on  
the squeakland.org about people page).

I'm not sure I wired it up, but we can make team members the only ones  
able to schedule and prioritize an issue.

These are typically tasks performed by project managers ... in our  
case, the team is the "project manager".

Limiting the size of the team just makes things more manageable,  
anyone can volunteer for the team.

Tim