Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.incubator.apache.org
From: ahgittin <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
References: <git-pr-92-incubator-brooklyn@git.apache.org>
In-Reply-To: <git-pr-92-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: Versioning catalog items
Content-Type: text/plain
Message-Id: <20140811040844.370BB9AA2BF@tyr.zones.apache.org>
Date: Mon, 11 Aug 2014 04:08:44 +0000 (UTC)

Github user ahgittin commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/92#issuecomment-51740421
  
    i think we agree at the two enpoints -- from user side, they are *not* required to supply a version; and in back-end everything *does* have a version wherever possible.  so if user specifies "MySoftware" brooklyn internally srtores that it is MySoftware_1.0.1 or whatever.
    
    it is the mapping in between that we are unsure of.  i don't like the 999.0.0 idea -- it is nice in some ways but feels an ugly "magic numbers" hack in others.  i also don't think that the intermediate/alias needs to be versioned -- as that is *not* what is stored (ie the alias is resolved at deploy time and not used anymore thereafter).  that should simplify things a big?


---
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.
---