> On Mon, Jan 14, 2013 at 4:28 PM, Frank Zhang <frank.zh...@citrix.com> > wrote: > > > >> > >> On Mon, Jan 14, 2013 at 4:06 PM, Frank Zhang <frank.zh...@citrix.com> > >> wrote: > >> > What's kind of update community prefer? Is pasting git commit > >> > message to > >> Jira good enough? > >> > >> So with my Release Manager hat on - I was looking to understand how > >> far along (roughly) everyone is. That's always hard to report, but > >> I've had success keeping it simple: not started, 25%, 50%, 75%, Done. > > > > I just look at Jira UI trying to find out a decent place to put status > percentage other than comments, but no luck. > > I think we can treat all issue without process started(by clicking 'start > process' button) as not started. > > +1 - Hopefully folks will click it! > > > It's also ok to put percentage in comment, but we should figure out > > what's the interval to report percentage? Will release manager > > periodically send out reminder ? :) > > Comments is perfect for me. I've been actually reminding each week. > This was the second week!
Sure, I will report my status in this way. And could we use some vivid tag in mail title like [STATUS UPDATE REMINDER]? Then I would not miss the important mail. Thanks > > Thanks Frank! > > > > > > >> > >> Basically, it's hard for me to tell what's in progress or not, and > >> how far along things are, without reading through the git commit logs > >> and attempting to guess on future work / intent. > >> > >> Does that make sense? > > > >> > >> -chip > >> > >> >> -----Original Message----- > >> >> From: Chip Childers [mailto:chip.child...@sungard.com] > >> >> Sent: Monday, January 14, 2013 12:14 PM > >> >> To: cloudstack-dev@incubator.apache.org > >> >> Subject: [ACS41] Feature and improvement updates please! > >> >> > >> >> Hi all, > >> >> > >> >> Just another friendly reminder to please update the new feature / > >> >> improvement jira records to indicate how you are doing on them! > >> >> It's helpful for everyone to know what looks like it will make it > >> >> in before the feature freeze, or may be something we have to > >> >> release in a > >> future release cycle. > >> >> > >> >> Thanks! > >> >> > >> >> -chip > >> > > >
