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 42EA3200CB6 for ; Thu, 29 Jun 2017 10:34:01 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 41500160BED; Thu, 29 Jun 2017 08:34:01 +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 7F038160BDF for ; Thu, 29 Jun 2017 10:34:00 +0200 (CEST) Received: (qmail 67577 invoked by uid 500); 29 Jun 2017 08:33:59 -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 67566 invoked by uid 99); 29 Jun 2017 08:33:58 -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; Thu, 29 Jun 2017 08:33:58 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id E6154DFB30; Thu, 29 Jun 2017 08:33:57 +0000 (UTC) From: geomacy To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #740: New versioning rules prep Content-Type: text/plain Message-Id: <20170629083357.E6154DFB30@git1-us-west.apache.org> Date: Thu, 29 Jun 2017 08:33:57 +0000 (UTC) archived-at: Thu, 29 Jun 2017 08:34:01 -0000 Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/740 I don't think there's any harm in having a slightly stricter validation in place, in fact as a user I would find that more helpful than having Brooklyn adapt to me doing things badly. Should we take the discussion of the above points back on to the mailing list or just deal with them here? --- 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. ---