Quick reminder:
1) If you have an issue at any time (independent of this announcement, or when the next release may be), you should make sure it is in the bug-tracker.
2) If you believe a bug report in the tracker may have been overlooked, you can always mention this. The best place for that is on the mail list. Issues of this kind on the forum may not get the full attention, as some team members are only/mainly on the mail list.
However this does not mean that everyone should constantly push there issues. The way a bug report and fix works is:
- report is made
- a team member (who maintains the related code or is familiar with it) will volunteer to take the issue (assign it to him).
- that team member then decides where the issue ends up in his personal priority (compared to other issues).
And when that team member has spare free time (between his job and personal live) he/she will work on it.
If no one assigned the issue to themself, then it may have been overlooked, in that case it makes sense to ask on the mail list (new issues should be given 2 or 3 weeks to be seen, even though often it goes faster)
It is possible that even then (after asking on the mail list) you do not get a response. The person may be away for some weeks, or busy otherwise.
-----------------------
This announcement/thread is not going to change this dynamics.
If an issue had been overlooked, then yes you should mention it, but it may well be that if it get picked up now, it will not have a fix in time and them may be pushed to 2.0.4.
Of course if the issue is easy enough to fix, then it may still get done in time.
However in the past we also had cases in which issues were fixed. But it had been forgotten to put them on the merge list.
Or available patches had not been reviewed.
In this cases it has happened that an available fix missed the release for no good reason. We are trying to minimize this. (Of course any other improvement that can reasonably be made for the release would be welcome too)