Hi all,
there are 100 bugs open for v3.1.1 and 75 for v3.1.2. We need to triage
this :). Please, everyone, take a look at all these bugs, and do one of
the following:
1) Close already resolved bugs, or bugs which can be closed as won't fix
or invalid.
2) Move bugs from v3.1.1 to v3.1.2 *or* to v3.3.0.
3) Move bugs from v3.1.2 to v3.3.0.
4) Do code reviews, and/or commit patches (and then go back to step 1).
I'm making an assumption here that we'll only make 2 more "unstable"
releases before v3.2, using v3.1.3 as a "final" test release. This makes
v3.3.0 the upcoming "test" release as well. This is to achieve the one
"major" release every 6 months as we've discussed many times, so we need
v3.2 around December time frame.
Thoughts and feedback?
-- Leif