We're overdue on our planning of 4.2.2. There are 109 open issues scheduled to be fixed in this patch release (admittedly, lots of them are assigned to me and I haven't had time to work on them). We do need to cut the release at some point though so I'm looking for suggestions on how to proceed.
Thanks Martin
