cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fang Wang <>
Subject RE: [DISCUSS] new workflow for new features....
Date Fri, 14 Dec 2012 18:02:40 GMT
For a  feature with several people working on it, if we create couple of bugs to track it,
shall we add
A field to point to a "master" bug to track the discussions, documents, etc?  
The master bug can contain all the proposal, discussions, etc. And the individual features
can be
Tracked in each sub bug, is it feasible? Or we want to track all feature development in the
Master bug?


-----Original Message-----
From: Alex Huang [] 
Sent: Friday, December 14, 2012 7:06 AM
Subject: RE: [DISCUSS] new workflow for new features....

> -----Original Message-----
> From: Mohammad Nour El-Din []
> Sent: Friday, December 14, 2012 6:17 AM
> To:
> Subject: Re: [DISCUSS] new workflow for new features....
> Hi
> On Fri, Dec 14, 2012 at 3:08 PM, Alex Huang <> wrote:
> > With the new feature proposals coming in for 4.1, I like to propose 
> > that we add a new workflow in Jira for new feature and improvement 
> > issue
> types.
> >
> > - At creation, it should be "Discuss".
> > - Once input has been gathered on the mailing list, it should move 
> > into "Discussed".  On this status, the URL to mail thread that 
> > discussed the requirements should be linked on the bug.
> > - Then a developer takes on the issue, changes it to "Propose".  
> > Emails should be sent to the lists on the proposal.
> > - When it is all done on the list, then it moves into "Open" and 
> > starts the current work flow.  As it moves into open, the developer 
> > should post the link to the mail thread that discussed the design proposal.
> >
> > What do everyone think?  For devs in other project, is there 
> > anything in other projects similar that we can just reuse?
> >
> The workflow looks detailed and captures the states of discussion and 
> proposed solution before digging into implementation, the only point I 
> take on it is that it needs a lot of attention and labor to take care 
> that new features go through this workflow, how can you guarantee that ?

Good question!  So I don't like to see this as something that people must do but as a way
to naturally give directions on what they should do.  I think on issues that are important
to the community, the community will naturally ask why hasn't this been done or can the requestor
or developer update the status of the issue or the community can update as a crowd.

The problem that I see today is that unless I monitor the mailing list 24x7 and has a noggin
the size of Einstein's, it is difficult to track what is going on.  And I waste a lot of time
tracking the same thing again and again.  If it is this way for me, I wonder what it is like
for a user who's interested in a certain issue and how they can keep track.  They can search
on the mailing list but often you're not sure if a conclusion actually has been reached. 
And then they have to do that on every issue they care about.  With this they can generate
their own filter and ask for status in a way that everyone understands.  And once the status
is provided, everyone else who's interested can also see it.

It's about giving everyone a common language they can use rather than dictating what they
have to do .


View raw message