Re: [VOTE] Move to Github issues
My bad, I just saw the e-mail to infra after replying to this one :( Thanks for taking the lead on this matter. On Fri, Mar 30, 2018 at 11:30 AM, Rohit Yadav wrote: > Rafael, yes I did see the other email to infra cc-ed to dev@. I've also > reopened a ticket. > > Get Outlook for Android<https://aka.ms/ghei36> > > > From: Rafael Weingärtner > Sent: Friday, March 30, 2018 4:53:57 PM > To: dev > Subject: Re: [VOTE] Move to Github issues > > Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already > experiment using it. > > On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav > wrote: > > > 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. Developers who have submitted PRs without a jira id > may > > be accepted now provided their PRs have a milestone and qualify merge > > guidelines (2 lgtms, test results etc). > > > > PS. Happy Easter! > > > > Regards. > > > > Get Outlook for Android<https://aka.ms/ghei36> > > > > ____________ > > From: Tutkowski, Mike > > Sent: Thursday, March 29, 2018 11:08:36 PM > > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > On 3/26/18, 12:33 AM, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > > - Developers can use #id references while fixing an existing/open > > issue in > > a PR [2]. PRs can be sent without requiring to open/create an issue. > > - Use Github milestone to track both issues and pull requests > towards a > > CloudStack release, and generate release notes. > > - Relax requirement for JIRA IDs, JIRA still to be used for > historical > > reference and security issues. Use of JIRA will be discouraged. > > - The current requirement of two(+) non-author LGTMs will continue > for > > PR > > acceptance. The two(+) PR non-authors can advise resolution to any > > issue > > that we've not already discussed/agreed upon. > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Vote will be open for 120 hours. If the vote passes the following > > actions > > will be taken: > > - Get Github features enabled from ASF INFRA > > - Update CONTRIBUTING.md and other relevant cwiki pages. > > - Update project website > > > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull- > > requests/ > > > > Regards, > > Rohit Yadav > > > > > > > > rohit.ya...@shapeblue.com > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > > -- > Rafael Weingärtner > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > -- Rafael Weingärtner
Re: [VOTE] Move to Github issues
Rafael, yes I did see the other email to infra cc-ed to dev@. I've also reopened a ticket. Get Outlook for Android<https://aka.ms/ghei36> From: Rafael Weingärtner Sent: Friday, March 30, 2018 4:53:57 PM To: dev Subject: Re: [VOTE] Move to Github issues Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already experiment using it. On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav wrote: > 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. Developers who have submitted PRs without a jira id may > be accepted now provided their PRs have a milestone and qualify merge > guidelines (2 lgtms, test results etc). > > PS. Happy Easter! > > Regards. > > Get Outlook for Android<https://aka.ms/ghei36> > > > From: Tutkowski, Mike > Sent: Thursday, March 29, 2018 11:08:36 PM > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > On 3/26/18, 12:33 AM, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull- > requests/ > > Regards, > Rohit Yadav > > > > rohit.ya...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > -- Rafael Weingärtner rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Re: [VOTE] Move to Github issues
Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already experiment using it. On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav wrote: > 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. Developers who have submitted PRs without a jira id may > be accepted now provided their PRs have a milestone and qualify merge > guidelines (2 lgtms, test results etc). > > PS. Happy Easter! > > Regards. > > Get Outlook for Android<https://aka.ms/ghei36> > > > From: Tutkowski, Mike > Sent: Thursday, March 29, 2018 11:08:36 PM > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > On 3/26/18, 12:33 AM, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull- > requests/ > > Regards, > Rohit Yadav > > > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > -- Rafael Weingärtner
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. Developers who have submitted PRs without a jira id may be accepted now provided their PRs have a milestone and qualify merge guidelines (2 lgtms, test results etc). PS. Happy Easter! Regards. Get Outlook for Android<https://aka.ms/ghei36> From: Tutkowski, Mike Sent: Thursday, March 29, 2018 11:08:36 PM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: Re: [VOTE] Move to Github issues +1 On 3/26/18, 12:33 AM, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. - Developers can use #id references while fixing an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Re: [VOTE] Move to Github issues
+1 On 3/26/18, 12:33 AM, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. - Developers can use #id references while fixing an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav
Re: [VOTE] Move to Github issues
+1 On Mon, 26 Mar 2018 at 21:25 Glenn Wagner wrote: > +1 > > glenn.wag...@shapeblue.com > www.shapeblue.com > Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape > Town 7129South Africa > @shapeblue > > > > > -Original Message- > From: David Mabry > Sent: Monday, 26 March 2018 4:51 PM > To: dev@cloudstack.apache.org > Cc: users > Subject: Re: [VOTE] Move to Github issues > > +1 > > On 3/26/18, 8:05 AM, "Will Stevens" wrote: > > +1 > > On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < > nicolas.vazq...@shapeblue.com> wrote: > > > +1 > > > > > > From: Dag Sonstebo > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonstebo > > Cloud Architect > > ShapeBlue > > > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking > issues. > > - Developers can use #id references while fixing an existing/open > > issue in > > a PR [2]. PRs can be sent without requiring to open/create an > issue. > > - Use Github milestone to track both issues and pull requests > towards a > > CloudStack release, and generate release notes. > > - Relax requirement for JIRA IDs, JIRA still to be used for > historical > > reference and security issues. Use of JIRA will be discouraged. > > - The current requirement of two(+) non-author LGTMs will > continue for > > PR > > acceptance. The two(+) PR non-authors can advise resolution to > any > > issue > > that we've not already discussed/agreed upon. > > > > For sanity in tallying the vote, can PMC members please be sure > to > > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Vote will be open for 120 hours. If the vote passes the following > > actions > > will be taken: > > - Get Github features enabled from ASF INFRA > > - Update CONTRIBUTING.md and other relevant cwik > <https://maps.google.com/?q=pdate+CONTRIBUTING.md+and+other+relevant+cwik&entry=gmail&source=g>i > pages. > > - Update project website > > > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > > [2] > > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > > > Regards, > > Rohit Yadav > > > > > > > > dag.sonst...@shapeblue.com > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > nicolas.vazq...@shapeblue.com > > www.shapeblue.com > > , > > @shapeblue > > > > > > > > > > >
RE: [VOTE] Move to Github issues
+1 glenn.wag...@shapeblue.com www.shapeblue.com Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town 7129South Africa @shapeblue -Original Message- From: David Mabry Sent: Monday, 26 March 2018 4:51 PM To: dev@cloudstack.apache.org Cc: users Subject: Re: [VOTE] Move to Github issues +1 On 3/26/18, 8:05 AM, "Will Stevens" wrote: +1 On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < nicolas.vazq...@shapeblue.com> wrote: > +1 > > > From: Dag Sonstebo > Sent: Monday, March 26, 2018 5:06:29 AM > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > Regards, > Rohit Yadav > > > > dag.sonst...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > nicolas.vazq...@shapeblue.com > www.shapeblue.com > , > @shapeblue > > > >
Re: [VOTE] Move to Github issues
+1 On 3/26/18, 8:05 AM, "Will Stevens" wrote: +1 On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < nicolas.vazq...@shapeblue.com> wrote: > +1 > > > From: Dag Sonstebo > Sent: Monday, March 26, 2018 5:06:29 AM > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > Regards, > Rohit Yadav > > > > dag.sonst...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > nicolas.vazq...@shapeblue.com > www.shapeblue.com > , > @shapeblue > > > >
Re: [VOTE] Move to Github issues
+1 On Mon, Mar 26, 2018 at 9:05 AM, Will Stevens wrote: > +1 > > On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < > nicolas.vazq...@shapeblue.com> wrote: > > > +1 > > > > > > From: Dag Sonstebo > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonstebo > > Cloud Architect > > ShapeBlue > > > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > > - Developers can use #id references while fixing an existing/open > > issue in > > a PR [2]. PRs can be sent without requiring to open/create an issue. > > - Use Github milestone to track both issues and pull requests > towards a > > CloudStack release, and generate release notes. > > - Relax requirement for JIRA IDs, JIRA still to be used for > historical > > reference and security issues. Use of JIRA will be discouraged. > > - The current requirement of two(+) non-author LGTMs will continue > for > > PR > > acceptance. The two(+) PR non-authors can advise resolution to any > > issue > > that we've not already discussed/agreed upon. > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Vote will be open for 120 hours. If the vote passes the following > > actions > > will be taken: > > - Get Github features enabled from ASF INFRA > > - Update CONTRIBUTING.md and other relevant cwiki pages. > > - Update project website > > > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > > [2] > > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > > > Regards, > > Rohit Yadav > > > > > > > > dag.sonst...@shapeblue.com > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > nicolas.vazq...@shapeblue.com > > www.shapeblue.com > > , > > @shapeblue > > > > > > > > >
Re: [VOTE] Move to Github issues
+1 On Mon, Mar 26, 2018 at 3:05 PM, Will Stevens wrote: > +1 > > On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < > nicolas.vazq...@shapeblue.com> wrote: > > > +1 > > > > > > From: Dag Sonstebo > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonstebo > > Cloud Architect > > ShapeBlue > > > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > > - Developers can use #id references while fixing an existing/open > > issue in > > a PR [2]. PRs can be sent without requiring to open/create an issue. > > - Use Github milestone to track both issues and pull requests > towards a > > CloudStack release, and generate release notes. > > - Relax requirement for JIRA IDs, JIRA still to be used for > historical > > reference and security issues. Use of JIRA will be discouraged. > > - The current requirement of two(+) non-author LGTMs will continue > for > > PR > > acceptance. The two(+) PR non-authors can advise resolution to any > > issue > > that we've not already discussed/agreed upon. > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Vote will be open for 120 hours. If the vote passes the following > > actions > > will be taken: > > - Get Github features enabled from ASF INFRA > > - Update CONTRIBUTING.md and other relevant cwiki pages. > > - Update project website > > > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > > [2] > > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > > > Regards, > > Rohit Yadav > > > > > > > > dag.sonst...@shapeblue.com > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > nicolas.vazq...@shapeblue.com > > www.shapeblue.com > > , > > @shapeblue > > > > > > > > >
Re: [VOTE] Move to Github issues
+1 (binding). From: Rohit Yadav Sent: Monday, March 26, 2018 1:33 AM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org 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 developers can use Github issues for tracking issues. - Developers can use #id references while fixing an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav
Re: [VOTE] Move to Github issues
+1 On Mon, Mar 26, 2018 at 6:05 AM Will Stevens wrote: > +1 > > On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < > nicolas.vazq...@shapeblue.com> wrote: > > > +1 > > > > > > From: Dag Sonstebo > > Sent: Monday, March 26, 2018 5:06:29 AM > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Subject: Re: [VOTE] Move to Github issues > > > > +1 > > > > Regards, > > Dag Sonstebo > > Cloud Architect > > ShapeBlue > > > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > > - Developers can use #id references while fixing an existing/open > > issue in > > a PR [2]. PRs can be sent without requiring to open/create an issue. > > - Use Github milestone to track both issues and pull requests > towards a > > CloudStack release, and generate release notes. > > - Relax requirement for JIRA IDs, JIRA still to be used for > historical > > reference and security issues. Use of JIRA will be discouraged. > > - The current requirement of two(+) non-author LGTMs will continue > for > > PR > > acceptance. The two(+) PR non-authors can advise resolution to any > > issue > > that we've not already discussed/agreed upon. > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate > > "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Vote will be open for 120 hours. If the vote passes the following > > actions > > will be taken: > > - Get Github features enabled from ASF INFRA > > - Update CONTRIBUTING.md and other relevant cwiki pages. > > - Update project website > > > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > > [2] > > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > > > Regards, > > Rohit Yadav > > > > > > > > dag.sonst...@shapeblue.com > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > nicolas.vazq...@shapeblue.com > > www.shapeblue.com > > , > > @shapeblue > > > > > > > > >
Re: [VOTE] Move to Github issues
+1 On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, < nicolas.vazq...@shapeblue.com> wrote: > +1 > > > From: Dag Sonstebo > Sent: Monday, March 26, 2018 5:06:29 AM > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > Subject: Re: [VOTE] Move to Github issues > > +1 > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > Regards, > Rohit Yadav > > > > dag.sonst...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > nicolas.vazq...@shapeblue.com > www.shapeblue.com > , > @shapeblue > > > >
Re: [VOTE] Move to Github issues
+1 From: Dag Sonstebo Sent: Monday, March 26, 2018 5:06:29 AM To: us...@cloudstack.apache.org; dev@cloudstack.apache.org Subject: Re: [VOTE] Move to Github issues +1 Regards, Dag Sonstebo Cloud Architect ShapeBlue On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. - Developers can use #id references while fixing an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav dag.sonst...@shapeblue.com www.shapeblue.com<http://www.shapeblue.com> 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue nicolas.vazq...@shapeblue.com www.shapeblue.com , @shapeblue
Re: [VOTE] Move to Github issues
+1 On Mon, Mar 26, 2018 at 5:06 AM, Dag Sonstebo wrote: > +1 > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open > issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for > PR > acceptance. The two(+) PR non-authors can advise resolution to any > issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to > indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following > actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull- > requests/ > > Regards, > Rohit Yadav > > > > dag.sonst...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > -- Rafael Weingärtner
Re: [VOTE] Move to Github issues
+1 Regards, Dag Sonstebo Cloud Architect ShapeBlue On 26/03/2018, 07:33, "Rohit Yadav" 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 user and developers can use Github issues for tracking issues. - Developers can use #id references while fixing an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav dag.sonst...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Re: [VOTE] Move to Github issues
+1 > On 26 Mar 2018, at 10:21, Nux! wrote: > > +1 > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > boris.stoya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue - Original Message - >> From: "Rohit Yadav" >> To: "dev" , "users" >> Sent: 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 developers can use Github issues for tracking issues. >> - Developers can use #id references while fixing an existing/open issue in >> a PR [2]. PRs can be sent without requiring to open/create an issue. >> - Use Github milestone to track both issues and pull requests towards a >> CloudStack release, and generate release notes. >> - Relax requirement for JIRA IDs, JIRA still to be used for historical >> reference and security issues. Use of JIRA will be discouraged. >> - The current requirement of two(+) non-author LGTMs will continue for PR >> acceptance. The two(+) PR non-authors can advise resolution to any issue >> that we've not already discussed/agreed upon. >> >> For sanity in tallying the vote, can PMC members please be sure to indicate >> "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Vote will be open for 120 hours. If the vote passes the following actions >> will be taken: >> - Get Github features enabled from ASF INFRA >> - Update CONTRIBUTING.md and other relevant cwiki pages. >> - Update project website >> >> [1] https://markmail.org/message/llodbwsmzgx5hod6 >> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ >> >> Regards, >> Rohit Yadav
Re: [VOTE] Move to Github issues
+1 -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Rohit Yadav" > To: "dev" , "users" > Sent: 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 developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for PR > acceptance. The two(+) PR non-authors can advise resolution to any issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > Regards, > Rohit Yadav
Re: [VOTE] Move to Github issues
+1
Re: [VOTE] Move to Github issues
+1 On 03/26/2018 08:33 AM, Rohit Yadav 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 user and developers can use Github issues for tracking issues. > - Developers can use #id references while fixing an existing/open issue in > a PR [2]. PRs can be sent without requiring to open/create an issue. > - Use Github milestone to track both issues and pull requests towards a > CloudStack release, and generate release notes. > - Relax requirement for JIRA IDs, JIRA still to be used for historical > reference and security issues. Use of JIRA will be discouraged. > - The current requirement of two(+) non-author LGTMs will continue for PR > acceptance. The two(+) PR non-authors can advise resolution to any issue > that we've not already discussed/agreed upon. > > For sanity in tallying the vote, can PMC members please be sure to indicate > "(binding)" with their vote? > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Vote will be open for 120 hours. If the vote passes the following actions > will be taken: > - Get Github features enabled from ASF INFRA > - Update CONTRIBUTING.md and other relevant cwiki pages. > - Update project website > > [1] https://markmail.org/message/llodbwsmzgx5hod6 > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ > > Regards, > Rohit Yadav >
[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 an existing/open issue in a PR [2]. PRs can be sent without requiring to open/create an issue. - Use Github milestone to track both issues and pull requests towards a CloudStack release, and generate release notes. - Relax requirement for JIRA IDs, JIRA still to be used for historical reference and security issues. Use of JIRA will be discouraged. - The current requirement of two(+) non-author LGTMs will continue for PR acceptance. The two(+) PR non-authors can advise resolution to any issue that we've not already discussed/agreed upon. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open for 120 hours. If the vote passes the following actions will be taken: - Get Github features enabled from ASF INFRA - Update CONTRIBUTING.md and other relevant cwiki pages. - Update project website [1] https://markmail.org/message/llodbwsmzgx5hod6 [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/ Regards, Rohit Yadav