-1 at the moment because I think this is a bit premature. I think when attempting a release, we should at least have a quick email to ask the other devs if there's anything left that needs to be resolved before we can take a vote.
For example, there were a lot of issues moved to 1.2, but SHIRO-186 and SHIRO-197 have both been implemented but not yet resolved. I left them open on purpose in case we needed to do some additional work based on users' testing. Since we've received no feedback for them, they can be marked resolved and included in 1.1. Just a quick "hey, let's try to cut a release on Friday - let's clean up anything that might need to happen in the next day or two" would be nice. I'd like to go through the moved issues today, resolve the ones that I know have been open but should be resolved, and then take a re-vote if that's ok. Les
