I've been a bit silent. As several new issues were brought forward I have not attempted to create a new RC yet. The most pressing one is that volumes can get lost during migrate on vmware and a fix is being devised as we write. I will update you at the end of the week.
On Thu, Mar 2, 2023 at 10:07 AM Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > Thanks Daan, looking at the outstanding issues/PRs list here are some > suggestions that you can help triage and include in RC3: > > https://github.com/apache/cloudstack/pull/7302 > https://github.com/apache/cloudstack/pull/7304 > https://github.com/apache/cloudstack/pull/7268 (needs manual > QA/regression test) > https://github.com/apache/cloudstack/pull/7291 (needs manual > QA/regression test) > https://github.com/apache/cloudstack/pull/7237 (PR author to advise if > this is critical?) > https://github.com/apache/cloudstack/pull/7229 (not sure if this causes a > critical billing/usage issue?) > > > Regards. > > ________________________________ > From: Daan Hoogland <daan.hoogl...@gmail.com> > Sent: Thursday, March 2, 2023 14:31 > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Cc: users <us...@cloudstack.apache.org>; PMC < > priv...@cloudstack.apache.org> > Subject: Re: [4.18][RELEASE] RC2 up for vote > > unfortunately I am -1 myself :( > > Last night Marcus and Wei explored a security issue in the new feature of > volume encryption. A fix is underway. I will create an RC3 asap. > Please reply here with any other critical issues you want included in the > next release candidate? > > regard, > > On Wed, Mar 1, 2023 at 5:29 PM Vladimir Petrov < > vladimir.pet...@shapeblue.com> wrote: > > > Hi all, > > > > +1, I tested different upgrades (from 4.15, 4.16 and 4.17 using different > > hypervisors) and the common operations and found no issues. > > > > Best wishes, > > Vladi > > > > > > > > Daan Hoogland wrote: > > > > > > Hi All, > > some small errata, > > - I added my key > > - I will keep this vote open till friday, we've had a weekend and being > > lenient on those 72 hours will not hurt the quality, I think. > > It has taken some time but; > > > > I've created a second 4.18.0.0 release candidate, with the following > > artifacts up for a vote: > > > > Git Branch and Commit > > SH: > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.18.0.0-RC20230224T1301 > > Commit: 77961d6aa583a347b289af4cbb732b77c8be8ebe > > > > Source release (checksums and signatures are available at the following > > location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.0.0/ > > > > PGP release keys (signed using > > 256ABDFB8D89EDE07540BE6ACEF9E802B86FEED4): > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > Vote will be open for at least 72 hours. > > > > For sanity in tallying the vote, can PMC members please be sure to > > indicate "(binding)" with their vote? > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > > > > > > > -- > Daan > > > > -- Daan