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 56FD7200B7E for ; Tue, 23 Aug 2016 01:02:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 55A3B160ABC; Mon, 22 Aug 2016 23:02:25 +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 C2B98160AB3 for ; Tue, 23 Aug 2016 01:02:24 +0200 (CEST) Received: (qmail 36875 invoked by uid 500); 22 Aug 2016 23:02:23 -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 36858 invoked by uid 99); 22 Aug 2016 23:02:22 -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; Mon, 22 Aug 2016 23:02:22 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id D2492DFB89; Mon, 22 Aug 2016 23:02:22 +0000 (UTC) From: jburwell To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1647: [lts] CLOUDSTACK-9462: Systemd support for Ubuntu 16... Content-Type: text/plain Message-Id: <20160822230222.D2492DFB89@git1-us-west.apache.org> Date: Mon, 22 Aug 2016 23:02:22 +0000 (UTC) archived-at: Mon, 22 Aug 2016 23:02:25 -0000 Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1647 @wido While I understand that it is quite old and presents maintenance challenges, it remains supported until [April 2017](https://wiki.ubuntu.com/Releases). Therefore, it would be reasonable for users to expect us to continue to support it until EOL. I have opened conversation on dev@ and user@ in an effort to determine the impact (if any) to users post 4.9. In the meantime, would it be possible to split this PR into Ubuntu 16.04 support and removal of Ubuntu 12.04 support? If we decide to remove it, I propose that we introduce it in the 4.10.x release. Not only is 4.9 an LTS branch, it doesn't seem reasonable to drop support for a distribution in a patch release (i.e. 4.9.0.0 supports Ubuntu 12.04 and 4.9.1.0 does not). Conversely, Ubuntu 16.04 support seems like a worthy addition to LTS. Splitting these two issues will provide the flexibility to implement such removal of Ubuntu 12.04 in 4.10.x and the addition of Ubuntu 16.04 in 4.9.x+. Does this approach seem reasonable? --- 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. ---