Hi Senaka,
On Sat, Sep 7, 2013 at 10:26 PM, Senaka Fernando <[email protected]> wrote: > Hi all, > > This is gentle reminder for the newer people in the QA team. Please make > sure to provide clear steps to reproduce issues. Even though you find a > very useful issue, if the developer cannot reproduce it based on your > explanation, then it is hard or sometimes impossible to fix. If you not > sure as to how to report the steps, please do have a chat with a senior > person from the QA team. > We usually follow this approach but due to the release rush, we may have missed this for a few issues. In such situations, we have discussed the issue with the relevant developers and helped them to reproduce the issue. However, we will make sure we follow this strictly in future. > When there are documentation available on how things are done, please > refer to them and report issues if they don't work as expected. > Yes. We report documentation JIRAs in such situations. Thanks, Evanthika > In such situations please quote the documentation that you referred to > and explain what didn't work. Please also be mindful that some > configurations or approach to make changes to configuration may change from > release to release and therefore be sure to follow the latest documentation. > > Thanks, > Senaka. > > -- > * <http://us13.wso2con.com/> > * > * > * > *Senaka Fernando* > Senior Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
