Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6E00E2009DC for ; Tue, 2 May 2017 11:31:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6CA30160BAC; Tue, 2 May 2017 09:31:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AAE24160BA1 for ; Tue, 2 May 2017 11:30:59 +0200 (CEST) Received: (qmail 42216 invoked by uid 500); 2 May 2017 09:30:58 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 42205 invoked by uid 99); 2 May 2017 09:30:57 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2017 09:30:57 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id E4449DFD43; Tue, 2 May 2017 09:30:56 +0000 (UTC) From: aledsage To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #363: YOML = YAML object mapping language [BIG!] Content-Type: text/plain Message-Id: <20170502093056.E4449DFD43@git1-us-west.apache.org> Date: Tue, 2 May 2017 09:30:56 +0000 (UTC) archived-at: Tue, 02 May 2017 09:31:00 -0000 Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/363 @ahgittin with such a huge pull request, I think we should definitely stick with review before merging. We are hopefully going to find time next week to review this properly, with a concrete plan for how more members of the community would become familiar with this large code base, to build on and maintain it long term. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---