Hi Sravya, I think the latter approach may be easier to manage. And if we keep the ‘design_doc’ label, it may provide a more convenient way for people to check the design doc at any time. Thanks!
Best, Hao On Thu, May 5, 2016 at 10:54 AM, Sravya Tirukkovalur <[email protected]> wrote: > Thats a great suggestion Hao! I think we can achieve that by using labels. > But I am wondering what would the suggested workflow look like? > Label new feature jiras with "Design_review" and remove it when we have an > agreement on the design? One problem is design can be changed until the > patch is committed right? Or by default, have all new feature jiras have a > design doc attached? > > Thanks, > > On Mon, May 2, 2016 at 6:48 PM, Hao Hao <[email protected]> wrote: > > > Thanks a lot Sravya! This is really pretty useful. One comment for the > > dashboard: similar to code review queues, can we have a label or status > for > > “Design Review” to track the new features Jira that have designs need to > be > > reviewed? > > > > Best, > > Hao > > > > On Mon, May 2, 2016 at 6:35 PM, Sravya Tirukkovalur <[email protected]> > > wrote: > > > > > Hi all, > > > > > > Thought it might be useful to have a dashboard that we all share for > the > > > project to understand what is on the review and triage queues. We can > > also > > > use it to facilitate our monthly hangouts. Here is a link. Please let > me > > > know what else you would like to see. > > > > > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12323282 > > > > > > I was thinking of having a way to see community progress with respect > to > > > the following, but could not figure a reasonable way to do it. Any > > feedback > > > appreciated. > > > 1. Quick response on new jiras: Important to encourage new reporters/ > > > requests > > > 2. Quick turn around time for patches: Important for fellow developers. > > > > > > Regards, > > > > > > > > > -- > Sravya Tirukkovalur >
