Re: Github Issues

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

+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: d...@cloudstack.apache.org Cc: users Subject: Re: Github Issues Github

Re: Github Issues

oject are doing. The bad thing here is that you might end up with too > > > many labels. Maybe @resmo can give his point of view on how things are > > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of > > > labels, lots of issues and PRs). I don't know

Re: Github Issues

i All, > > > > We have been trialling replacing Jira with Github Issues. I think that > > we should have a conversation about it before it become the new standard > by > > default. > > > > From my perspective, I don't like it. Searching has become far more > &g

Re: Github Issues

I deleted my github account due to the change in ownership. Andrew On Tue, Jul 17, 2018 at 4:53 AM Paul Angus wrote: > Hi All, > > We have been trialling replacing Jira with Github Issues. I think that > we should have a conversation about it before it become the new standard

Re: Github Issues

ew on how things are > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of > labels, lots of issues and PRs). I don't know if that's a solution but > labels seem the only way to organize things. Personally, I don't care much if jira or github issues. Github issues worked prett

Re: Github Issues

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

Re: Github Issues

with Github Issues. I think that we should have a conversation about it before it become the new standard by default. From my perspective, I don't like it. Searching has become far more difficult, categorising has also. When there is a bug fix it can only be targeted for a single version, which

Re: Github Issues

eem the only way to organize things. Marc-Aurèle On Tue, Jul 17, 2018 at 10:53 AM, Paul Angus wrote: > Hi All, > > We have been trialling replacing Jira with Github Issues. I think that > we should have a conversation about it before it become the new standard by > de

Github Issues

Hi All, We have been trialling replacing Jira with Github Issues. I think that we should have a conversation about it before it become the new standard by default. From my perspective, I don't like it. Searching has become far more difficult, categorising has also. When there is a bug fix

Re: Request to enable Github issues, wiki for apache/cloudstack* repos

Enabled for your repos: https://issues.apache.org/jira/browse/INFRA-16186 Cheers On Mon, Apr 2, 2018 at 1:23 PM, Rohit Yadav wrote: > Ping infra? > > - Rohit > > On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav wrote: >> >> All, >> >> Based on a vote [1] on

Re: Request to enable Github issues, wiki for apache/cloudstack* repos

Ping infra? - Rohit On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav wrote: > All, > > Based on a vote [1] on Apache CloudStack MLs, I would like to request > infra to enable Github issue and wiki features for all cloudstack > repositories: > >

Request to enable Github issues, wiki for apache/cloudstack* repos

All, Based on a vote [1] on Apache CloudStack MLs, I would like to request infra to enable Github issue and wiki features for all cloudstack repositories: https://github.com/apache?q=cloudstack+ [1] https://markmail.org/message/y5zgkssmwp4sh43t Regards, Rohit Yadav PMC member and committer,

Re: [VOTE] Move to Github issues

Thanks all, after 5days the vote *passes* with all in favour of the proposal. I'll request infra immediately to enable the Github features for us, and update the website/docs over the next few days. After issues is available, users should use Github issues for logging bugs/features etc

Re: [VOTE] Move to Github issues

+1 On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote: All, Based on the discussion last week [1], I would like to start a vote to put the proposal into effect: - Enable Github issues, wiki features in CloudStack repositories. - Both use

Re: [VOTE] Move to Github issues

gt; > -Original Message- > From: David Mabry <dma...@ena.com.INVALID> > Sent: Monday, 26 March 2018 4:51 PM > To: d...@cloudstack.apache.org > Cc: users <users@cloudstack.apache.org> > Subject: Re: [VOTE] Move to Github issues > > +1 > > On 3/26/18,

RE: [VOTE] Move to Github issues

To: d...@cloudstack.apache.org Cc: users <users@cloudstack.apache.org> Subject: Re: [VOTE] Move to Github issues +1 On 3/26/18, 8:05 AM, "Will Stevens" <wstev...@cloudops.com> wrote: +1 On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < nicolas.vazq...@shap

Re: [VOTE] Move to Github issues

nstebo <dag.sonst...@shapeblue.com> > Sent: Monday, March 26, 2018 5:06:29 AM > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > Regards, > Dag Sonstebo > Cloud Architect

Re: [VOTE] Move to Github issues

Dag Sonstebo <dag.sonst...@shapeblue.com> > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonste

Re: [VOTE] Move to Github issues

stebo <dag.sonst...@shapeblue.com> > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonste

Re: [VOTE] Move to Github issues

+1 (binding). From: Rohit Yadav <ro...@apache.org> Sent: Monday, March 26, 2018 1:33 AM To: d...@cloudstack.apache.org; users@cloudstack.apache.org Subject: [VOTE] Move to Github issues All, Based on the discussion last week [1], I would like to start

Re: [VOTE] Move to Github issues

+1 From: Dag Sonstebo <dag.sonst...@shapeblue.com> Sent: Monday, March 26, 2018 5:06:29 AM To: users@cloudstack.apache.org; d...@cloudstack.apache.org Subject: Re: [VOTE] Move to Github issues +1 Regards, Dag Sonstebo Cloud Architect ShapeBlue On 26/03/20

Re: [VOTE] Move to Github issues

sed on the discussion last week [1], I would like to start a vote to > put > the proposal into effect: > > - Enable Github issues, wiki features in CloudStack repositories. > - Both user and developers can use Github issues for tracking issues. > - Developers can use

Re: [VOTE] Move to Github issues

+1 Regards, Dag Sonstebo Cloud Architect ShapeBlue On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote: All, Based on the discussion last week [1], I would like to start a vote to put the proposal into effect: - Enable Github issue

Re: [VOTE] Move to Github issues

N 4HSUK @shapeblue - Original Message - >> From: "Rohit Yadav" <ro...@apache.org> >> To: "dev" <d...@cloudstack.apache.org>, "users" <users@cloudstack.apache.org> >> Sent: Monday, 26 March, 2018 07:33:08 >> Subject: [VO

Re: [VOTE] Move to Github issues

t: Monday, 26 March, 2018 07:33:08 > Subject: [VOTE] Move to Github issues > All, > > Based on the discussion last week [1], I would like to start a vote to put > the proposal into effect: > > - Enable Github issues, wiki features in CloudStack repositories. > - Both user and

[VOTE] Move to Github issues

All, Based on the discussion last week [1], I would like to start a vote to put the proposal into effect: - Enable Github issues, wiki features in CloudStack repositories. - Both user and developers can use Github issues for tracking issues. - Developers can use #id references while fixing