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 102B610995 for ; Tue, 25 Nov 2014 16:37:21 +0000 (UTC) Received: (qmail 6808 invoked by uid 500); 25 Nov 2014 16:37:18 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 6714 invoked by uid 500); 25 Nov 2014 16:37:18 -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 6690 invoked by uid 99); 25 Nov 2014 16:37:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 16:37:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trippie@gmail.com designates 209.85.212.171 as permitted sender) Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com) (209.85.212.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 16:37:12 +0000 Received: by mail-wi0-f171.google.com with SMTP id bs8so9690650wib.16 for ; Tue, 25 Nov 2014 08:36:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=J6A9nWZlsgKW60YGI5mrnkVbRum+zfSrzkWyiltXYt4=; b=VQ32UzGyOXPKOO/UrU0gUVajwFzMK9oJYJHyf7zTjOBbzvex/vTkAh+Ednt04mrid1 rXmr6PY8Zz5itAY+jIYqyMSP7EIi40GkKirPUefV3xSJwoY6WRjI00o4UsVSfgSMW+WS HzAuOKgjz63Xa2ebj0cWJb97H+W/UagNE2r12akcsJJ6CaKso1vef4SPaicNdWuXJhFz aZA6LQ75Z9co/B+fxHzDz68DYi3EKdwQLn1cBJQcshv8sgi5+zYS2uSm4O0SAUPpEiMp JZ9MIBTlsZJzgYd8MojoFyDvZF0ezvdUyAJMguiZzr7H7DsI/MvsCzzaClYwFii4KFLd PXZw== X-Received: by 10.180.198.52 with SMTP id iz20mr6105462wic.60.1416933354485; Tue, 25 Nov 2014 08:35:54 -0800 (PST) Received: from [10.10.1.108] ([95.142.96.53]) by mx.google.com with ESMTPSA id hs1sm17176914wib.1.2014.11.25.08.35.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Nov 2014 08:35:53 -0800 (PST) Sender: Trippie From: Hugo Trippaers X-Google-Original-From: Hugo Trippaers Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: [DISCUSS] LTS Releases In-Reply-To: <0A510AFE-A633-4B8A-AC05-C58E951442DF@shapeblue.com> Date: Tue, 25 Nov 2014 17:35:51 +0100 Cc: "users@cloudstack.apache.org" Content-Transfer-Encoding: quoted-printable Message-Id: <4831C6E4-5164-4E07-AD05-769F012EEC0B@GMAIL.com> References: <1633077854.21374.1416920945439.JavaMail.zimbra@li.nux.ro>

<0A510AFE-A633-4B8A-AC05-C58E951442DF@shapeblue.com> To: dev@cloudstack.apache.org X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org Top posting here as my remarks are mainly on the original topic. I=E2=80=99m not in favor of supporting LTS releases as a community. The = reasoning here is that there is a huge chance that we will fragment the = community in people that just want to work on the latest and greatest = and some other folks who are trying to keep older releases from being = updated with newer fixes. It requires a lot of dedicated commitment to = keep an LTS release going. Particularly if you yourself are already = working with a newer release in your environment. So from a personal = standpoint i can almost guarantee that i will probably not spend the = time and effort of back porting any fixes i do to older versions of = CloudStack. That doesn=E2=80=99t mean that it can=E2=80=99t happen. If people are = willing to take charge of an LTS branch and are willing to do the work = to back port fixes where appropriate i would happily support them and = even try to test the releases so we can have an official release.=20 New developers might also be scared by the fact that a fix they make has = to be supported on multiple branches and might decide not to commit such = a fix because of the work involved. With the rate of change in the code = at the moment this is also very hard for seasoned developers, so much = little, but important stuff changes all the time that back porting is = very difficult. It is an open source project and generally people will = want to focus on the latest and greatest and just get their features in. = I=E2=80=99m already regularly having some trouble back porting between = master and 4.5. Consider back porting to master, 4.5 and 4.3 as well and = having to test each branch. Basically my point is, everyone who wants to LTS support a certain = branch is free to do so. Whether or not other contributors or committers = will want to do that is their choice. As a community we should not make = any promises about LTS support for a certain branch.=20 Cheers, Hugo > On 25 nov. 2014, at 16:16, Rohit Yadav = wrote: >=20 > Hey Daan, >=20 >> On 25-Nov-2014, at 7:26 pm, Daan Hoogland = wrote: >>=20 >> That is worrying, Rohit. As the rest of your mail is already a vote = of >> distrust, this part says we should not release 4.4.2 as it contains >> regressions. >=20 > Looks like you skimmed my email and missed the following from my = previous email: > =E2=80=9CNote: This is not to say that 4.4.x is not stable, we=E2=80=99r= e simply saying we recommend 4.3.x because we have a confidence of its = stability and we encourage serious CloudStack users to use it.=E2=80=9D >=20 > 4.4.x is probably the greatest ACS feature release ever but I would = still recommend conservative users (who consult me) to stick to 4.3.x = for production since we know it just works with least amount of pain. = The other issue is I know a lot of people who are on ACS 4.3.x still = (including ShapeBlue=E2=80=99s customers) want to have bugfix releases = and they may not want to migrate to 4.4.x right now since 4.5.x is about = 2=E2=80=933 months away. >=20 > ACS when consumed by enterprise companies has a typical lifecycle that = lasts at least 6 months, that means someone needs to support it, = therefore the idea of official LTS releases. >=20 >> This is a very bad signal to users and the rest of the >> community. What you are saying is (you in transitive form), 'we won't >> port fixes to 4.4 but only to 4.3 so upgrade to newer 4.3 versions = and >> not to a 4.4 version. You have the right to do so but I don't like = it. >=20 > In any form I did not say anything about not helping out or not = porting things. People who know me, know that I love to help everyone = and I=E2=80=99m quite prompt at reply and resolving things. I=E2=80=99ve = taken the task to maintain 4.3 and you=E2=80=99re very welcome to go = thorough JIRA etc. to backport things that you want for 4.4 since = you=E2=80=99re alone the gatekeeper of this branch. >=20 > I=E2=80=99m going through these bugs that have a different fix version = (not 4.3.0 or 4.3.1): = https://issues.apache.org/jira/issues/?filter=3D12329775 >=20 > Wido suggested that backporting is time consuming so as a challenge = I=E2=80=99ve went through 50 issues today, I was able to = understand/backport about 25 of them that qualified for 4.3 branch (many = of them were trivial, = https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;a=3Dcommit;h=3D= f72eb945540e607ff25917922b4084187246f31a), about 10 of them were hard to = backport so I=E2=80=99ve asked authors to help out. I think with this = speed I alone should be able to go through like 300 issues reported on = JIRA in about 10-15 days time and after than about 10-20 days of testing = and getting the bugfix release out. Though if we all help out we can get = more mileage. >=20 > It sucks for me personally that I=E2=80=99ve been emailing you = privately about cherry-pick and asking you to pick them on 4.4 (also = leaving messages on JIRA). I=E2=80=99ll continue to do that :) and = meanwhile, you are very welcome to go see the things I picked on 4.3 and = pick those applicable on 4.4. >=20 > Yours friendly and as always, >=20 > Rohit Yadav > Software Architect, ShapeBlue > M. +91 88 262 30892 | rohit.yadav@shapeblue.com > Blog: bhaisaab.org | Twitter: @_bhaisaab >=20 > Find out more about ShapeBlue and our range of CloudStack related = services >=20 > IaaS Cloud Design & = Build > CSForge =E2=80=93 rapid IaaS deployment = framework > CloudStack Consulting > CloudStack Software = Engineering > CloudStack Infrastructure = Support > CloudStack Bootcamp Training = Courses >=20 > This email and any attachments to it may be confidential and are = intended solely for the use of the individual to whom it is addressed. = Any views or opinions expressed are solely those of the author and do = not necessarily represent those of Shape Blue Ltd or related companies. = If you are not the intended recipient of this email, you must neither = take any action based upon its contents, nor copy or show it to anyone. = Please contact the sender if you believe you have received this email in = error. Shape Blue Ltd is a company incorporated in England & Wales. = ShapeBlue Services India LLP is a company incorporated in India and is = operated under license from Shape Blue Ltd. Shape Blue Brasil = Consultoria Ltda is a company incorporated in Brasil and is operated = under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company = registered by The Republic of South Africa and is traded under license = from Shape Blue Ltd. ShapeBlue is a registered trademark.