cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Parth Patel <parthpatel2...@gmail.com>
Subject Re: [VOTE] Move to Github issues
Date Mon, 26 Mar 2018 16:49:54 GMT
+1

On Mon, 26 Mar 2018 at 21:25 Glenn Wagner <glenn.wagner@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 <dmabry@ena.com.INVALID>
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users <users@cloudstack.apache.org>
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> ´╗┐On 3/26/18, 8:05 AM, "Will Stevens" <wstevens@cloudops.com> wrote:
>
>     +1
>
>     On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
>     Nicolas.Vazquez@shapeblue.com> wrote:
>
>     > +1
>     >
>     > ________________________________
>     > From: Dag Sonstebo <Dag.Sonstebo@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" <rohit@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
>     >
>     >
>     >
>     >
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message