Update
If you have any issue/regression that you believe needs to be addressed before the Release of 2.2 make sure it is reported on the
issue tracker and it is
included in the Version 2.2 milestone
This includes any issue already mentioned in this thread (unless already fixed and merged).
If you are unsure of an issue you are welcome to discuss it here on the forum (in this thread or any other). If you do not get feedback then it might be best to just report it. Keep in mind that the later the report, the lower the chances something will be done about it.
Where not obvious, please include (in the issue) the reason, why you believe it should be 2.2.
If you report new issues, you may have the option to set the milestone yourself as a suggestion.
Any properties (milestone, labels, ...) are treated as suggestions, and will be reviewed and removed if not agreed on by a developer.
Because issues are often "high prior" to their reporter, any such "importance" properties will usually just be removed. Those fields are reserved for developers only.
If you can not apply the milestone yourself, post the link to the issue in this thread here.I will then apply the milestone. It will then be reviewed by a team member who maintains the relevant code section (so if found not a 2.2 issue, it will be removed again)
Please note, all milestone are treated as "loose targets". Issues will be addressed, if our manpower permits. The team will decide at its own discretion if or how long to hold the release for an issue. Or if to move an issues target.