Agree with the ideal world scenario :-)
If we look at it from the other side: Why is it that people want to stay on
older releases?
From personal experience I know that in the beginning the 4.4 release wasn’t
that stable. I upgraded production systems from 4.3.0 to 4.4.2 and it was
painful. Th
On Jul 3, 2015, at 11:13 AM, Rene Moser wrote:
> Sebastien,
>
> So wouldn't it be nice to make clear which release is still supported
> and which release is not?
>
> On 03.07.2015 09:20, sebgoa wrote:
>
>> I think we got in a situation with 4.4 that called for us to keep
>> maintaining 4.3….
Sebastien,
So wouldn't it be nice to make clear which release is still supported
and which release is not?
On 03.07.2015 09:20, sebgoa wrote:
> I think we got in a situation with 4.4 that called for us to keep maintaining
> 4.3….and even after 4.5 was released. Because 4.3 was seen as a good re
On Jul 2, 2015, at 4:58 PM, Remi Bergsma wrote:
> Bug fixing in older releases is actually a lot of work. For security related
> issues we could maybe do it.
>
> Personally, I prefer to have a fast release cycle and smooth (tested) upgrade
> paths over 2-year LTS release cycle. It's more agi
Bug fixing in older releases is actually a lot of work. For security related
issues we could maybe do it.
Personally, I prefer to have a fast release cycle and smooth (tested) upgrade
paths over 2-year LTS release cycle. It's more agile. As a bonus, people get
the new features.
The more peop
Maybe a little bit off topic to the new release process, therefor a new
thread...
speaking about releases. I just thought about supporting LTS releases.
This would mean "someone" or "we" make a commitment to add bug fixes
(only) for a specified time. e.g. 2 years for a release or until the
next L
Hi everyone,
Thanks for a great discussion.
I understand it may be difficult to support releases for several years with
CloudStack’s fast paced development, and the statistics Leo shared are
certainly not what I was aiming for.
I think it will be difficult to gather agreement in this stage and
Hey hey,
Ooh, interesting topic. I'm going to top-post because I want to focus on the
big picture!
* Apache HTTPD provides 8+ years of support for old releases.
* Tomcat provides 6+ years of support for N-2 release.
* Ant provides 12+ years of backward compatiblity, so far.
(details below)
I th
-- Original --
From: "Andrei Mikhailovsky";
Date: Thu, Nov 27, 2014 08:51 PM
To: "dev";
Subject: Re: [DISCUSS] LTS Releases
ChunFeng,
I think as long as there is a change to the current efforts it will improve the
stability of the product. At th
want to have a
production ready system and they perhaps be less likely to install and test the
non-LTS release.
Andrei
- Original Message -
> From: "ChunFeng"
> To: "dev"
> Sent: Thursday, 27 November, 2014 10:36:46 AM
> Subject: Re: [DISCUSS] LTS Releas
ING,
POLISHING ", "then LTS becomes less important" and " I’m not in favor of
supporting LTS releases as a community. "
--
Regards,
ChunFeng
-- Original --
From: "sebgoa";
Date: Thu, Nov 27, 2014
kporting issues
>already and I hope many developers will join this effort.
Andrei
- Original Message -
> From: "Andrija Panic"
> To: dev@cloudstack.apache.org
> Sent: Thursday, 27 November, 2014 8:01:41 AM
> Subject: Re: [DISCUSS] LTS Releases
> my 2 cent
On Nov 27, 2014, at 9:01 AM, Andrija Panic wrote:
> my 2 cents again:
>
> Whether we have this LTS release or not - is not just about having release
> - we need a WAY to focus here on FIXING, POLISHING product and more
> important to stimulate/make developers interested in doing so.
> If this w
my 2 cents again:
Whether we have this LTS release or not - is not just about having release
- we need a WAY to focus here on FIXING, POLISHING product and more
important to stimulate/make developers interested in doing so.
If this was company owned product, it would be very easy to set goals, and
I'm not really in favor of LTS support, it's a good idea, but not sure it
can be backed by the community?[open question here ;)]. I don't think it
fit in our current model for few reasons:
- Upgrade path might become impossible as patches become part of multiple
versions. We could end up with prob
- Original Message -
> Hi,
> During CCCEU14 conference and over emails, I spoke with many
> CloudStack users and I think most of us would like to have and use
> LTS releases. I propose that;
> - We encourage a habit to backport a bugfix to all qualifying
> branches whether or not those b
Top posting here as my remarks are mainly on the original topic.
I’m 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
Rohit, I consider you my friend and colleague, I could reply on
everything said but do not want to escalate on all the details. The
only remark I want to make is that 4.4 is open for commits from here
on in.
On Tue, Nov 25, 2014 at 4:16 PM, Rohit Yadav wrote:
> Hey Daan,
>
>> On 25-Nov-2014, at 7
Hey Daan,
> On 25-Nov-2014, at 7:26 pm, Daan Hoogland wrote:
>
> 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.
Looks like you skimmed my email and missed the following from my previous e
On Tue, Nov 25, 2014 at 3:47 PM, Nux! wrote:
> I like 4.4 better than 4.3 for my use case and despite the bugs I hit it does
> its job.
> If I were to deploy today it would still be with 4.4. Hope this makes you
> feel better. :-)
It makes me feel the hero;) Seriously, I don't feel bad about 4
...@cloudstack.apache.org
Subject: Re: [DISCUSS] LTS Releases
Daan,
I like 4.4 better than 4.3 for my use case and despite the bugs I hit it does
its job.
If I were to deploy today it would still be with 4.4. Hope this makes you feel
better. :-)
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux
-
> From: "Daan Hoogland"
> To: "dev"
> Cc: us...@cloudstack.apache.org
> Sent: Tuesday, 25 November, 2014 13:56:12
> Subject: Re: [DISCUSS] LTS Releases
> On Tue, Nov 25, 2014 at 2:40 PM, Rohit Yadav
> wrote:
>> The 4.4 branch does not contain many
rant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Rohit Yadav"
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Sent: Tuesday, 25 November, 2014 13:40:23
> Subject: Re: [DISCUSS] LTS Releases
> Hi Wido and Lucian,
>
&g
On Tue, Nov 25, 2014 at 2:40 PM, Rohit Yadav wrote:
> The 4.4 branch does not contain many bugfixes which are in 4.3 and on
> master/4.5.
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. This
ck and see how 4.5 goes and start with that one?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Rohit Yadav"
>> To: "dev"
>> Cc: us...@cloudstack.apache.org
it Yadav"
> To: "dev"
> Cc: us...@cloudstack.apache.org
> Sent: Tuesday, 25 November, 2014 11:30:53
> Subject: [DISCUSS] LTS Releases
> Hi,
>
> During CCCEU14 conference and over emails, I spoke with many CloudStack users
> and I think most of us wou
Hi,
On 11/25/2014 12:30 PM, Rohit Yadav wrote:
> Hi,
>
> During CCCEU14 conference and over emails, I spoke with many CloudStack users
> and I think most of us would like to have and use LTS releases. I propose
> that;
>
> - We encourage a habit to backport a bugfix to all qualifying branches
Hi,
During CCCEU14 conference and over emails, I spoke with many CloudStack users
and I think most of us would like to have and use LTS releases. I propose that;
- We encourage a habit to backport a bugfix to all qualifying branches whether
or not those branches are LTS
- We contribute (unit, i
28 matches
Mail list logo
