Hi Daan, Can we start a different thread cutting a new RC on 4.19.2.0, if those fixes accepted in 4.19 branch (after RC1) must make into 4.19.2.0? Please also specify the RC number on the subject to avoid confusions, thanks.
Regards. ________________________________ From: Daan Hoogland <d...@apache.org> Sent: Tuesday, February 4, 2025 13:53 To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: [VOTE] release candidate 4.19.2.0 Bernardo, First thanks for your feedback. On Mon, Feb 3, 2025 at 7:51 PM Bernardo De Marco Gonçalves < bernardomg2...@gmail.com> wrote: > Hello Daan, all > > I got a little bit confused with the fact that the RC for the 4.19.2.0 > release was opened for voting and, in the meantime, we were still working > and merging bug fixes PRs targeting the 4.19 branch. This is not the usual > procedure we adopt for the release process. > Actually it is, the only difference is that I didn't call for a hard freeze because of the large number of open PRs. Sorry for the confusion though. I believe that it would be interesting to freeze the 4.19 branch and then > release a new RC for voting. Then, we all can focus 100% on testing the > upcoming release. If you guys need any help testing/reviewing any > additional PRs that are supposed to be merged into the 4.19 branch, just > let me know that I'll try to help. > I would like us to be able to release without a hard freeze. We can do that but apart from a major release and for critical bugs or blockers, I don't think we need to. We always need more testing help ;) There are however still going to be PRs and issues open for the 4.19 branch. If there is the general consensus that people want to have a new RC I will certainly make one. Not at the moment though because an instability crept into the branch after RC0. Best regards, > Bernardo De Marco Gonçalves (bernardodemarco) > ... > > El 3/2/2025 a las 06:26, Daan Hoogland escribió: > > > > LS, > > > > > > > > I've had no reactions. I can say "no news is good news" or be a > > > pessimist. > > > > Did anybody at all have a look yet? The 72 hours are way gone, and we > > > had a > > > > weekend as well. > > > > > > > > On Tue, Jan 28, 2025 at 10:52 AM Daan Hoogland<d...@apache.org> > wrote: > > > > > > > >> LS, > > > >> I uploaded convenience packages to > > > >> https://download.cloudstack.org/testing/4.19.2.0-RC20250128T0916/ > for > > > >> those interested. > > > >> > > > >> > > > >> On Tue, Jan 28, 2025 at 9:28 AM Daan Hoogland<d...@apache.org> > wrote: > > > >> > > > >>> Hi All, > > > >>> > > > >>> I've created a 4.19.2.0 release, with the following artifacts up > for > > a > > > vote: > > > >>> > > > >>> Git Branch and Commit SH: > > > >>> > > > > https://github.com/apache/cloudstack/tree/4.19.2.0-RC20250128T0916Commit > > : > > > 5c6b04f6bfcca575492e97f32a6d1d23b49bdffc > > > >>> > > > >>> Source release (checksums and signatures are available at the same > > > >>> location): > > https://dist.apache.org/repos/dist/dev/cloudstack/4.19.2.0/ > > > >>> > > > >>> PGP release keys (signed using > > > 256ABDFB8D89EDE07540BE6ACEF9E802B86FEED4): > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > >>> > > > >>> Vote will be open for 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) > > > >>> > > > >>> > > > >>> I am in the process of creating convenience packages and will > update > > on > > > >>> those in this mail-thread. > > > >>> > > > >>> regards, > > > >>> >
