working on the release.
>
> 3.1.2. Voting may take four flavors:
> 3.1.2.1.+1 "Yes," "Agree," or "the action should be performed." In
> general, this vote also indicates a willingness on the behalf of the voter
> in "making it happen"
>
med." In
general, this vote also indicates a willingness on the behalf of the voter in
"making it happen"
http://cloudstack.apache.org/bylaws.html
Kind regards
Paul Angus
-Original Message-
From: Gabriel Bräscher
Sent: 10 September 2021 14:15
To: dev
Subject
sts across three hypervisors - that is not to say no release has no
> reported issues (in fact they all do 🙂).
>
>
> Regards.
>
> ____
> From: Gabriel Bräscher
> Sent: Wednesday, September 8, 2021 18:39
> To: dev
> Subject: Re: [Discussion] Release Cycle
>
> Th
eases (but
> without the promise of upgrade paths) -
> http://download.cloudstack.org/testing/nightly/
>
>
> 5. finally - I would say if you or anyone wants to work on a release (call
> it whatever, regular, LTS) - just propose and do!
>
>
> Regards.
>
> _
ths) -
> http://download.cloudstack.org/testing/nightly/
>
>
> 5. finally - I would say if you or anyone wants to work on a release (call
> it whatever, regular, LTS) - just propose and do!
>
>
> Regards.
>
>
> From: Daniel Augusto Veron
s) -
http://download.cloudstack.org/testing/nightly/
5. finally - I would say if you or anyone wants to work on a release (call it
whatever, regular, LTS) - just propose and do!
Regards.
From: Daniel Augusto Veronezi Salvador
Sent: Tuesday, September 7, 202
Hi Gabriel, thanks for opening this discussion.
I'm +1 on it. My considerations:
- We've to put a lot of efforts to support 3+ LTS simultaneously, which
doesn't make sense. Regular versions will give us some breath and will
reduce rework.
- Although the EOL is well defined, it seems we don't h
1:37 PM
To: dev
Subject: Re: [Discussion] Release Cycle
I like the notion of LTS every 2 years and having 1 or 2 regular releases per
year, like the Ubuntu model.
Typically, upgrading our cloud from a major release is a big level of effort,
especially around QA to make sure the upgrade does
I like the notion of LTS every 2 years and having 1 or 2 regular releases
per year, like the Ubuntu model.
Typically, upgrading our cloud from a major release is a big level of
effort, especially around QA to make sure the upgrade does not affect
customers.
So, having to jump between LTS every ye
Hi Gabriel,
1. I'm a +1 on having regular releases between LTS ones and the reasoning
behind it. While stability is great, it will also be nice to have a "pilot" as
you mentioned which the community can test and issues are resolved in the
following LTS, rather than waiting for 2 - 3 release
10 matches
Mail list logo
