+1 for what Henry said. Recently, several JIRA issues were opened without a detailed description but which were immediately addressed by a pull request. This is probably because our coding guidelines state that each PR should refer to a JIRA issue [1]. The rational behind this guideline is to have a JIRA ticket for documentation to which the commit message links. Without a proper description of the issue, this purpose is not met.
I would like to ask everybody to provide descriptions that help to understand the issue. Thanks, Fabian [1] http://flink.apache.org/coding-guidelines.html 2015-08-16 10:35 GMT+02:00 Henry Saputra <henry.sapu...@gmail.com>: > Hi All, > > Apology for the cross-posting. > > Please remember to add detail Description in the JIRA ticket to help > reproduce and prioritize the issues. > Assume that some other people will try to solve and reproduce the issues. > > Adding information in JIRA issues is to help describe the issue and > steps to reproduce. > Adding information in Github PR is to describe how and what being > changed or added to solve the problem. > > We will add guide about adding more Description and step to reproduce > for JIRA issues in the how to contribute page [1] to promote open and > transparent development in Apache Flink. > > > Thanks, > > - Henry > > > [1] https://flink.apache.org/how-to-contribute.html >
