Since it is a rather nasty bug due to a typo on my behalf, do we push a
release (2.2.1) now to include the fix and push all the unfixed issues back
to 2.3 (where they currently live)

-Stephen

Reply via email to