You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Rohit Yadav <ro...@apache.org> on 2018/03/26 06:33:08 UTC
[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
Posted by Boris Stoyanov <bo...@shapeblue.com>.
+1
> On 26 Mar 2018, at 10:21, Nux! <nu...@li.nux.ro> wrote:
>
> +1
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
boris.stoyanov@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
----- Original Message -----
>> From: "Rohit Yadav" <ro...@apache.org>
>> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
>> 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
Posted by Boris Stoyanov <bo...@shapeblue.com>.
+1
> On 26 Mar 2018, at 10:21, Nux! <nu...@li.nux.ro> wrote:
>
> +1
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
boris.stoyanov@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
----- Original Message -----
>> From: "Rohit Yadav" <ro...@apache.org>
>> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
>> 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
Posted by Nux! <nu...@li.nux.ro>.
+1
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Rohit Yadav" <ro...@apache.org>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> 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
Posted by Nux! <nu...@li.nux.ro>.
+1
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Rohit Yadav" <ro...@apache.org>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> 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
Posted by Simon Weller <sw...@ena.com.INVALID>.
+1 (binding).
________________________________
From: Rohit Yadav <ro...@apache.org>
Sent: Monday, March 26, 2018 1:33 AM
To: dev@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 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
Posted by Wido den Hollander <wi...@widodh.nl>.
+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
>
Re: [VOTE] Move to Github issues
Posted by Rene Moser <ma...@renemoser.net>.
+1
Re: [VOTE] Move to Github issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
+1
On Mon, Mar 26, 2018 at 5:06 AM, Dag Sonstebo <Da...@shapeblue.com>
wrote:
> +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 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.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
--
Rafael Weingärtner
Re: [VOTE] Move to Github issues
Posted by Syed Ahmed <sa...@cloudops.com>.
+1
On Mon, Mar 26, 2018 at 6:05 AM Will Stevens <ws...@cloudops.com> wrote:
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
Re: [VOTE] Move to Github issues
Posted by Khosrow Moossavi <km...@cloudops.com>.
+1
On Mon, Mar 26, 2018 at 9:05 AM, Will Stevens <ws...@cloudops.com> wrote:
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
Re: [VOTE] Move to Github issues
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
+1
On Mon, Mar 26, 2018 at 3:05 PM, Will Stevens <ws...@cloudops.com> wrote:
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
Re: [VOTE] Move to Github issues
Posted by Parth Patel <pa...@gmail.com>.
+1
On Mon, 26 Mar 2018 at 21:25 Glenn Wagner <gl...@shapeblue.com>
wrote:
> +1
>
> glenn.wagner@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 <dm...@ena.com.INVALID>
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users <us...@cloudstack.apache.org>
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
>
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
>
>
Re: [VOTE] Move to Github issues
Posted by Parth Patel <pa...@gmail.com>.
+1
On Mon, 26 Mar 2018 at 21:25 Glenn Wagner <gl...@shapeblue.com>
wrote:
> +1
>
> glenn.wagner@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 <dm...@ena.com.INVALID>
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users <us...@cloudstack.apache.org>
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
>
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
>
>
RE: [VOTE] Move to Github issues
Posted by Glenn Wagner <gl...@shapeblue.com>.
+1
glenn.wagner@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 <dm...@ena.com.INVALID>
Sent: Monday, 26 March 2018 4:51 PM
To: dev@cloudstack.apache.org
Cc: users <us...@cloudstack.apache.org>
Subject: Re: [VOTE] Move to Github issues
+1
On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
Nicolas.Vazquez@shapeblue.com> wrote:
> +1
>
> ________________________________
> From: Dag Sonstebo <Da...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@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" <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 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.Sonstebo@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>
RE: [VOTE] Move to Github issues
Posted by Glenn Wagner <gl...@shapeblue.com>.
+1
glenn.wagner@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 <dm...@ena.com.INVALID>
Sent: Monday, 26 March 2018 4:51 PM
To: dev@cloudstack.apache.org
Cc: users <us...@cloudstack.apache.org>
Subject: Re: [VOTE] Move to Github issues
+1
On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
Nicolas.Vazquez@shapeblue.com> wrote:
> +1
>
> ________________________________
> From: Dag Sonstebo <Da...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@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" <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 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.Sonstebo@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>
Re: [VOTE] Move to Github issues
Posted by David Mabry <dm...@ena.com.INVALID>.
+1
On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
Nicolas.Vazquez@shapeblue.com> wrote:
> +1
>
> ________________________________
> From: Dag Sonstebo <Da...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@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" <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 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.Sonstebo@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>
Re: [VOTE] Move to Github issues
Posted by Khosrow Moossavi <km...@cloudops.com>.
+1
On Mon, Mar 26, 2018 at 9:05 AM, Will Stevens <ws...@cloudops.com> wrote:
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
Re: [VOTE] Move to Github issues
Posted by David Mabry <dm...@ena.com.INVALID>.
+1
On 3/26/18, 8:05 AM, "Will Stevens" <ws...@cloudops.com> wrote:
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
Nicolas.Vazquez@shapeblue.com> wrote:
> +1
>
> ________________________________
> From: Dag Sonstebo <Da...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@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" <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 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.Sonstebo@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>
Re: [VOTE] Move to Github issues
Posted by Marc-Aurèle Brothier <ma...@exoscale.ch>.
+1
On Mon, Mar 26, 2018 at 3:05 PM, Will Stevens <ws...@cloudops.com> wrote:
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> Nicolas.Vazquez@shapeblue.com> wrote:
>
> > +1
> >
> > ________________________________
> > From: Dag Sonstebo <Da...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: users@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" <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 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.Sonstebo@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > Nicolas.Vazquez@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
Re: [VOTE] Move to Github issues
Posted by Will Stevens <ws...@cloudops.com>.
+1
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
Nicolas.Vazquez@shapeblue.com> wrote:
> +1
>
> ________________________________
> From: Dag Sonstebo <Da...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@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" <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 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.Sonstebo@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>
Re: [VOTE] Move to Github issues
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
+1
________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Monday, March 26, 2018 5:06:29 AM
To: users@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" <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 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.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Nicolas.Vazquez@shapeblue.com
www.shapeblue.com
,
@shapeblue
Re: [VOTE] Move to Github issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
+1
On Mon, Mar 26, 2018 at 5:06 AM, Dag Sonstebo <Da...@shapeblue.com>
wrote:
> +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 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.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
--
Rafael Weingärtner
Re: [VOTE] Move to Github issues
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
+1
________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Monday, March 26, 2018 5:06:29 AM
To: users@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" <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 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.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Nicolas.Vazquez@shapeblue.com
www.shapeblue.com
,
@shapeblue
Re: [VOTE] Move to Github issues
Posted by Dag Sonstebo <Da...@shapeblue.com>.
+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 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.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [VOTE] Move to Github issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <ro...@shapeblue.com>
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 <ra...@gmail.com>
> 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 <ro...@shapeblue.com>
> 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 <Mi...@netapp.com>
> > Sent: Thursday, March 29, 2018 11:08:36 PM
> > To: dev@cloudstack.apache.org; users@cloudstack.apache.org
> > Subject: 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 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.yadav@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
>
> --
> Rafael Weingärtner
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
--
Rafael Weingärtner
Re: [VOTE] Move to Github issues
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <ra...@gmail.com>
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 <ro...@shapeblue.com>
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 <Mi...@netapp.com>
> Sent: Thursday, March 29, 2018 11:08:36 PM
> To: dev@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: 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 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.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
--
Rafael Weingärtner
rohit.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [VOTE] Move to Github issues
Posted by Rafael Weingärtner <ra...@gmail.com>.
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 <ro...@shapeblue.com>
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 <Mi...@netapp.com>
> Sent: Thursday, March 29, 2018 11:08:36 PM
> To: dev@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: 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 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.yadav@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
--
Rafael Weingärtner
Re: [VOTE] Move to Github issues
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <Mi...@netapp.com>
Sent: Thursday, March 29, 2018 11:08:36 PM
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Subject: 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 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.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [VOTE] Move to Github issues
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <Mi...@netapp.com>
Sent: Thursday, March 29, 2018 11:08:36 PM
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Subject: 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 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.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [VOTE] Move to Github issues
Posted by "Tutkowski, Mike" <Mi...@netapp.com>.
+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 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
Posted by Simon Weller <sw...@ena.com.INVALID>.
+1 (binding).
________________________________
From: Rohit Yadav <ro...@apache.org>
Sent: Monday, March 26, 2018 1:33 AM
To: dev@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 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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
+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 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.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [VOTE] Move to Github issues
Posted by "Tutkowski, Mike" <Mi...@netapp.com>.
+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 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