Hi, The 2.3.1 release vote failed to reach 3 +1s, so I'm dropping that release candidate. Instead I'm about to cut another release candidate, 2.3.2, from the trunk today.
Going forward I was thinking of adopting a two-week schedule of unstable releases from the trunk. This gives us a steady stream of releases, but requires some extra review work from the PMC. The release review script that Alex wrote should help there. We can scale back the release frequency if the overhead seems too high. BR, Jukka Zitting
