That is written from the point of view of a developer.
From someone who has no desire to ever see the code, let alone change
it, EOL has a big impact.
In a normal project, in the period prior to EOL, the developers commit
to fixing bugs and issuing security notices with resolutions.
Cloudstack will have a hard time gaining traction outside the companies
that develop it, if EOL has no meaning.
I worry that the lack of control over the roadmap and the apparent lack
of commitment to EOL means that, as good as Cloudstack may be, it is not
a system for production use unless the user is prepared to take on the
long-term maintenance at a moments notice and live with uncertainty
about future viability.
A bit harsh but the conversation about EOL is disturbing.
Ron
On 3/15/19 11:04 AM, Giles Sirett wrote:
Yes - I see your point
I think the thing to bear in mind here is that there is no *formal* EOL for an ACS
version or branch - its open source - EOL effectively means that people have lost the
interest in maintaining that branch. If people see a demand for more releases on a
branch in order to maintain that branch longer- then I'd think it unlikely that anybody
here is going to say "no"
maybe the wording in the wiki is misleading
Kind regards
Giles
giles.sir...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-----Original Message-----
From: Jean-Francois Nadeau <the.jfnad...@gmail.com>
Sent: 15 March 2019 12:49
To: dev@cloudstack.apache.org
Cc: Riepl, Gregor (SWISS TXT) <gregor.ri...@swisstxt.ch>
Subject: Re: Any plan for 4.11 LTS extension ?
I can only agree with Haijiao, that 4.11 deserves a longer time span.
Because many bugs are found naturally between the .0 and .1 of the next LTS
release with it's adoption.
For us 4.11 could only be adopted with 4.11.2.0 after several bugs needed
to get resolved. So if 4.11's support stops in July then it's time span
was only 6 months from our perspective.
-jfn
On Fri, Mar 15, 2019 at 5:34 AM Wido den Hollander <w...@widodh.nl> wrote:
On 3/15/19 10:20 AM, Riepl, Gregor (SWISS TXT) wrote:
Hi Giles,
I would *expect* 4.13.0 (LTS) to be released in Q2, which will
supersede the 4.11 branch as the current LTS branch
Are you confident that this schedule can be kept?
4.12 is still in RC right now, and I don't think it's a good idea to
rush another major release in just 3 months...
4.11.3 will be released first with some bugfixes to keep 4.11 a proper
release.
4.12 needs to go out now so that we can test and prepare for 4.13. I'm
confident we can have a stable and proper 4.13 release as long as we
don't keep the window open for too long.
The major problem is having the master branch open for a long time,
features going in and people not testing it sufficiently.
By having a relatively short period between 4.12 and 4.13 we can catch
most bugs and stabilize for a proper LTS.
Wido
