The way the issues are distributed in Jira are a bit confusing.
A CR3 release leads me to believe that is is almost ready, yet there 233 open issues.
I watch all the RF releases and it seems that the bulk of these bugs will just be rolled over to 3.2.2.
Why not split these out earlier so that users can more easily see what will be resolved in the 3.2.1 release?
A Jira issue does not mean a bug literally. We use it to schedule sub-tasks as well. If you set "No Component" in the filter, the number will more accurate.
Usually, the whole QA period in divided into two major phases: Bulk Fixing and Stabilization. The stabilization phase is about 20% of the whole QA. In the beginning of this phase, we sort the issues into two categories. The ones that could not potentially destabilize the upcoming release are scheduled for fixing in the upcoming release. The rest ones are moved forward.
We did not sort the issues yet. So, CR3 is not a last CR before the GA