Hi All,
I’ve raised a PR to add XenServer 7.1 and 7.2 to CloudStack’s hypervisor list
and added new OS mappings.
I’ve also not added deprecated OSes to the new mappings (if that makes sense).
https://github.com/apache/cloudstack/pull/2346
Tests pass with PR rebased to master as of a couple of
Is there a document (wiki page?) that captures the discussion about what
was missed in the release of 4.10?
Ron
On 13/12/2017 9:53 AM, Ivan Kudryavtsev wrote:
Hi, Rene.
That sounds great, chaos engineering and controlled experiments are great
tools, smoke tests improvements are also subject o
Hi, Paul. Thank you for your response. I just still feel that it's a very
risky approach to deliver a new release if community haven't adopted and
tried a previous one because future unidentified regressions are multiplied
to currently unidentified regressions. But, I see it's a trade and
controver
Hi, Rene.
That sounds great, chaos engineering and controlled experiments are great
tools, smoke tests improvements are also subject of discussion and I think
that UAT (user acceptance tests) suite should be designed finally. It's
important to a business to have one. It's important to the communit
Thanks Rene.
@Ivan, I understand your concerns. But if 4.10 is unusable, then it will never
get much production testing.
The longer between releases, the harder testing and triage becomes.
By putting a line in the sand for 4.11 and 4.12, and with the desire to keep
making every release better t
Hi all
On 12/13/2017 05:04 AM, Ivan Kudryavtsev wrote:
> Hello, devs, users, Rohit. Have a good day.
>
> Rohit, you intend to freeze 4.11 on 8 january and, frankly speaking, I see
> risks here. A major risk is that 4.10 is too buggy and it seems nobody uses
> it actually right now in production b
