The 3.2-RC1 did not reveal any problems that were blocking a release. Thus, we were skipping 3.2-RC2, until some community members brought some requests AFTER we had already skipped 3.2-RC2. Along these fixes being requested, internal parallel activities and the need for more testing, we are re-visiting the schedule according to this:

12/03/2025 - 3.2-RC2
26/03/2025 - 3.2 Release

We understand that this may frustrate some users, but on the positive side, many others will get important fixes.

Finally, this was the first round of releases under the new process. We will be adjusting the future dates to better reflect the lessons learned so far.