Hi Wei,

thanks for your hard work!

Would it be possible to merge #9460 ? This bug is bugging us ;-) As far as I 
can tell there's a patch regarding that issue and maybe it could be merged 
quite easily?



Am Tue, Sep 16, 2025 at 03:11:26PM +0200 schrieb Wei ZHOU:
> I forgot to say, if you have any major issues to fix or code changes to
> commit to the 4.20.2.0 release, please let me know.
> 
> 
> Kind regards,
> Wei
> 
> 
> On Tue, Sep 16, 2025 at 2:34 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> 
> > Hi all,
> >
> > Due to some security issues, we have to postpone the 4.20.2.0 RC1.
> >
> > The branch is again open for new commits. We will keep you updated on the
> > new code freeze date and RC1 date.
> >
> >
> > Kind regards,
> > Wei
> >
> >
> > On Tue, Sep 16, 2025 at 8:44 AM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> In the past week, 15 pull requests have been merged into the 4.20 branch.
> >>
> >> The code freeze date of 4.20.2.0 release is due. Thanks all for the
> >> support.
> >>
> >> I will cut 4.20.2.0-RC1 today.
> >>
> >>
> >>
> >> Kind regards,
> >> Wei
> >>
> >> On Tue, Sep 9, 2025 at 8:30 AM Wei ZHOU <weiz...@apache.org> wrote:
> >>
> >>> Hi all,
> >>>
> >>> In the past week, we have tested and merged 12 pull requests into the
> >>> 4.20 branch. Currently there are 88 open issues and 39 open pull requests
> >>>
> >>>
> >>> https://github.com/apache/cloudstack/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A4.20.2
> >>>
> >>>
> >>> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.20.2
> >>>
> >>> The code freeze time is  *September 15th (2025-09-15) 23:59 UTC.*
> >>>
> >>>
> >>> Kind regards,
> >>> Wei
> >>>
> >>>
> >>> On Tue, Sep 2, 2025 at 8:22 AM Wei ZHOU <weiz...@apache.org> wrote:
> >>>
> >>>> Hi community,
> >>>>
> >>>> Since CloudStack 4.19 is EOL, I have moved all issues and pull requests
> >>>> in the 4.19.4 milestone to 4.20.2 milestone.
> >>>>
> >>>> Currently there are 94 open issues and 78 open pull requests
> >>>>
> >>>>
> >>>> https://github.com/apache/cloudstack/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A4.20.2
> >>>>
> >>>>
> >>>> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.22.0
> >>>>
> >>>> You are very welcome to join the bug fixes and testing. The timeline of
> >>>> 4.20.2.0 release is not changed:
> >>>>
> >>>> - Code freeze on *September 15th (2025-09-15)*. No more code changes
> >>>> are accepted except for critical bug fixes (and sometimes security 
> >>>> patches).
> >>>> - Cut Release Candidate 1 (RC1) on *September 16th (2025-09-16)*.
> >>>>
> >>>>
> >>>> Kind regards,
> >>>> Wei
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Aug 21, 2025 at 2:45 PM Wei ZHOU <weiz...@apache.org> wrote:
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> The latest LTS version Apache CloudStack 4.20.1.0 was released on 10th
> >>>>> June.
> >>>>> Since then, around 70 issues have been fixed in the 4.20 branch.
> >>>>> I think it is time to create a new 4.20.2.0 release, so CloudStack
> >>>>> users can benefit from the work of the community.
> >>>>>
> >>>>> I propose myself as the release manager of 4.20.2.0 release. The
> >>>>> timeline of 4.20.2.0 release is listed as below:
> >>>>> - Code freeze on *September 15th (2025-09-15)*. No more code changes
> >>>>> are accepted except for critical bug fixes (and sometimes security 
> >>>>> patches).
> >>>>> - Cut Release Candidate 1 (RC1) on *September 16th (2025-09-16)*.
> >>>>>
> >>>>> I will manage the release through milestones on github
> >>>>> 4.19.4: https://github.com/apache/cloudstack/milestone/40 (most
> >>>>> issues also apply with 4.20)
> >>>>> 4.20.2: https://github.com/apache/cloudstack/milestone/39
> >>>>>
> >>>>> There are lots of open issues and pull requests, please feel free to
> >>>>> fix the issues. or review and test the pull requests. Thank you !
> >>>>>
> >>>>> If you have any questions, please let me know (by replying to this
> >>>>> email or mentioning @weizhouapache on github).
> >>>>>
> >>>>>
> >>>>>
> >>>>> Kind regards,
> >>>>> Wei
> >>>>>
> >>>>>
> >>>>>

Reply via email to