RE: [VOTE] Move to Github issues
Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town 7129South Africa
From: David Mabry <dmabry@xxxxxxx.INVALID>
Sent: Monday, 26 March 2018 4:51 PM
Cc: users <users@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [VOTE] Move to Github issues
On 3/26/18, 8:05 AM, "Will Stevens" <wstevens@xxxxxxxxxxxx> wrote:
On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> From: Dag Sonstebo <Dag.Sonstebo@xxxxxxxxxxxxx>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: users@xxxxxxxxxxxxxxxxxxxxx; dev@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [VOTE] Move to Github issues
> Dag Sonstebo
> Cloud Architect
> On 26/03/2018, 07:33, "Rohit Yadav" <rohit@xxxxxxxxxx> wrote:
> Based on the discussion last week , I would like to start a vote to
> 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 . 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
> acceptance. The two(+) PR non-authors can advise resolution to any
> that we've not already discussed/agreed upon.
> For sanity in tallying the vote, can PMC members please be sure to
> "(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
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>  https://markmail.org/message/llodbwsmzgx5hod6
> Rohit Yadav
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK