Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A7DF18C72 for ; Thu, 17 Dec 2015 03:17:25 +0000 (UTC) Received: (qmail 7527 invoked by uid 500); 17 Dec 2015 03:17:24 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 7467 invoked by uid 500); 17 Dec 2015 03:17:24 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 7452 invoked by uid 99); 17 Dec 2015 03:17:24 -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, 17 Dec 2015 03:17:24 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 2C08BDFCF2; Thu, 17 Dec 2015 03:17:24 +0000 (UTC) From: agneya2001 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ... Content-Type: text/plain Message-Id: <20151217031724.2C08BDFCF2@git1-us-west.apache.org> Date: Thu, 17 Dec 2015 03:17:24 +0000 (UTC) Github user agneya2001 commented on the pull request: https://github.com/apache/cloudstack/pull/823#issuecomment-165325933 @nitin-maharana @koushik-das @kishankavala @bhaisaab @jburwell @DaanHoogland @remibergsma Can we have a discussion on: Why do we need any kind of restriction on tags while looking for compatible service offering ? Is there any downside ? My opinion is we should just allow change of service offering irrespective of tags. --- 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. ---