incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <>
Subject Re: [ACS41] Can folks please take responsibility for updating their own Jira tickets?
Date Tue, 05 Feb 2013 21:52:59 GMT
Someone created sub-tickets for ours (QA, etc). It doesn't feel right
to close them until those pending subtasks are also completed. I made
a comment that the features were completed and merged, and assumed
that the owners of the sub tasks would update the ticket as well.

So perhaps at least some of it is just understanding how the flow is
supposed to work.

On Tue, Feb 5, 2013 at 2:45 PM, Animesh Chaturvedi
<> wrote:
>> -----Original Message-----
>> From: Chip Childers []
>> Sent: Tuesday, February 05, 2013 12:04 PM
>> To:
>> Subject: [ACS41] Can folks please take responsibility for updating their own Jira
>> tickets?
>> Hi all,
>> It's frustrating that folks aren't maintaining reasonable status / updates for
>> tickets assigned to themselves.  Sure, I'll keep looking through them and asking
>> questions as I go...  but wouldn't it be easier if you all just did it for the ones
>> that you own?  A little bit of personal ownership and responsibility goes a long
>> way to helping us all manage the releases.
>> Also - I'm not CC'ing anyone in particular here, because there are many people
>> that need to do this.  Spending the time to pull together that list is about the
>> same as spending the time actually reviewing status on everything.  Others
>> (Sudhap specifically) have asked for this same thing that I am, and I'm frankly
>> at a loss for how to get everyone's attention on this.
>> If you have jira records assigned to you, that are currently set for 4.1.0, can you
>> please either:
>> 1 - Update with the master branch commit -sh and confirm that it made it into
>> the 4.1 branch?
>> or
>> 2 - Update the fix version to be something other than 4.1.0?  Move the child
>> doc and QA (and other) tasks as well please!  Also, the wiki requirement and
>> design pages need to be moved to the correct parent page as well.
>> -chip
> [Animesh>] I agree it is frustrating as one person to go chase folks, and best done
by people taking their own responsibility.
> Having said that let me follow up on (1).
> On (2) I had already moved many features ahead of 1/31 and very few remaining were moved
on 1/31.

View raw message