Totally agree, more information in JIRA more easy for communication in community.
Would like to encourage each PMC member, committer and everyone to help check each JIRA and let the reporter to fulfill detail information for that. Thanks. Best Regards! --------------------- Luke Han On Fri, Sep 18, 2015 at 12:05 PM, Henry Saputra <[email protected]> wrote: > I think this one is good: KYLIN-1022 > and this one need more information: KYLIN-1028 > > - Henry > > On Thu, Sep 17, 2015 at 8:26 PM, Li Yang <[email protected]> wrote: > > Fully agree. Let's do that. > > > > In particular, any exiting JIRA needs more description? Any existing > JIRA > > is good and informative? Having examples will help people understand the > > level of details required. > > > > Cheers > > Yang > > > > On Fri, Sep 18, 2015 at 6:42 AM, Henry Saputra <[email protected]> > > wrote: > > > >> Hi All, > >> > >> To help increasing community participations, please add as much > >> information as possible when filing JIRAs. > >> > >> This will help people to understand how to reproduce and verify your > >> patch (if any). > >> > >> Some internal developers and committers may already know how the > >> problem is re-created but let exercise more discipline in filing > >> issues to benefit the community. > >> Assume that you are filing JIRA against other projects. You will not > >> be able to submit patch or get help if your JIRA is not descriptive. > >> > >> > >> Thanks, > >> > >> Henry > >> >
