That's a good idea, because people are more and more used to only create PR on github, and it would be helpful to be more explanatory on the way we work to push changes. I still think we should encourage the use of the github milestone as Rohit did with the 4.11.0 ( https://github.com/apache/cloudstack/milestone/3?closed=1) to list the changes in the release notes with the help of the labels to tag the PRs instead of relying on the jira ticket (it requires to have another login).
As far as I can remember, the JIRA tickets are used to list the changes of a release, but nothing else. Or am I missing something? Marc-Aurèle On Tue, Mar 13, 2018 at 9:57 AM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > All, > > > To make it easier for people to contribute changes and encourage > PR/contributions, should we relax the requirement of a JIRA ticket for pull > requests that solve trivial/minor issues such as doc bugs, build fixes etc? > A JIRA ticket may still be necessary for new features and non-trivial > bugfixes or changes. > > > Another alternative could be to introduce a CONTRIBUTING.md [1] that > explains the list of expected things to contributors when they send a PR > (for example, a jira id, links to fs or other resources, a short summary > and long description, test results etc). > > > Thoughts? > > > [1] https://help.github.com/articles/setting-guidelines- > for-repository-contributors/ > > > - Rohit > > <https://cloudstack.apache.org> > > > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > >
