Re: Github Issues

2018-07-23 Thread Rohit Yadav
Using Github issues is already a standard now, for reference this was the voting thread: https://markmail.org/message/y5zgkssmwp4sh43t I agree that Github milestone tagging on a pull request is limited to one per PR which I don't like as well. However, there is a workaround that may be used.

Re: Github Issues

2018-07-20 Thread Dingane Hlaluku
+1 as a new developer for this community, I find Github much easier for me to create/track both issues and PRs. From: Will Stevens Sent: Thursday, July 19, 2018 3:35:00 AM To: dev@cloudstack.apache.org Cc: users Subject: Re: Github Issues Github is the

Re: Github Issues

2018-07-18 Thread Will Stevens
Github is the platform that is most comfortable for most users and developers to collaborate. Everyone knows it, regardless of their background, so it opens our community to a wider group of people. Those are my thoughts anyway... Will On Wed, Jul 18, 2018, 2:10 PM Rafael Weingärtner < rafaelwei

Re: Github Issues

2018-07-18 Thread Rafael Weingärtner
There is something else that might be worth mentioning. Since we moved to Github, it seems that the project is attracting more people. I mean, it seems that there are new players coming and reporting issues and opening PRs. I might be totally mistaken though. On Wed, Jul 18, 2018 at 3:07 PM, Wi

Re: Github Issues

2018-07-18 Thread Will Stevens
+1 to access to better automation and integration. On Wed, Jul 18, 2018, 12:16 PM Rene Moser wrote: > Hi > > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote: > > Hi Paul, > > > > My 2 cents on the topic. > > > > people are commenting on issues when it should by the PR and vice-versa > >> > >

Re: Github Issues

2018-07-18 Thread Rene Moser
Hi On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote: > Hi Paul, > > My 2 cents on the topic. > > people are commenting on issues when it should by the PR and vice-versa >> > > I think this is simply due to the fact that with one login you can do both, > versus before you had to have a JIRA lo

Re: Github Issues

2018-07-17 Thread Khosrow Moossavi
I sort of agree with Marc-Aurèle and Will, and like github issues way better than Jira. It definitely is easier that both the issues and fix for those issues live in the same place and easily can be referenced from one another. The only thing is that we need to come up with good set of labels (for

Re: Github Issues

2018-07-17 Thread Will Stevens
Ron, keep in mind that PRs on Github are different from Issues. They are two different features. There will be a much cleaner, tighter integration between issues and the solution when everything is on Github. will On Tue, Jul 17, 2018, 9:33 AM Ron Wheeler wrote: > I may have voiced my concern

Re: Github Issues

2018-07-17 Thread Ron Wheeler
I may have voiced my concerns earlier but as a user, I think that JIRA issues are easier to follow than PRs. - As Paul said an issue may affect more than one version. - It may also require more than one PR to fully resolve the issue. - Issues tend to be described in terms of a problem that the us

Re: Github Issues

2018-07-17 Thread Marc-Aurèle Brothier
Hi Paul, My 2 cents on the topic. people are commenting on issues when it should by the PR and vice-versa > I think this is simply due to the fact that with one login you can do both, versus before you had to have a JIRA login which people might have tried to avoid, preferring using github direc