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 5245E200C23 for ; Wed, 22 Feb 2017 12:18:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 50DE7160B67; Wed, 22 Feb 2017 11:18:45 +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 91CAA160B49 for ; Wed, 22 Feb 2017 12:18:44 +0100 (CET) Received: (qmail 86577 invoked by uid 500); 22 Feb 2017 11:18:43 -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 86566 invoked by uid 99); 22 Feb 2017 11:18:43 -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; Wed, 22 Feb 2017 11:18:43 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4441CDFE1E; Wed, 22 Feb 2017 11:18:43 +0000 (UTC) From: koushik-das To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1951: CLOUDSTACK-9792: Add upgrade path for 4.9.3.0 Content-Type: text/plain Message-Id: <20170222111843.4441CDFE1E@git1-us-west.apache.org> Date: Wed, 22 Feb 2017 11:18:43 +0000 (UTC) archived-at: Wed, 22 Feb 2017 11:18:45 -0000 Github user koushik-das commented on the issue: https://github.com/apache/cloudstack/pull/1951 I already see schema-4920to41000.sql and the corresponding cleanup file in master. So how will this fit in the overall scheme? Is there any plans for 4.9.3? --- 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. ---