More bug fixes from master for the 0.10.1 release

[cap10morgan]

I'll start running this locally to see if I encounter any issues.

[bbatsov]

I'll keep this PR open for now, so we can add a bit more commits to it until the end of the week. Let's aim for a release of 0.10.1 early next week. I doubt that many people are at work between Christmas and New Year's Eve anyway, so the release is not super urgent.

[cap10morgan]

@bbatsov Sounds good. I'll keep pushing fixes until then.

[bbatsov]

Great!

[bbatsov]

We're good for a clojure-mode 5.1 release tomorrow and we'll probably do the cider 0.10.1 release then as well.

[bbatsov]

We'll also have to pull in the cider-nrepl part of 44a7ced.

[bbatsov]

This should also be part of 0.10.1 #1500

[cap10morgan]

@bbatsov Release schedule sounds good. Anything else I should bring in?

What's your usual testing process for a release? I'm going to fire this code up locally and kick it around a bit, but would be happy to apply a more comprehensive process if you have one.

[bbatsov]

Just do a bit of manual testing of the fixes we brought in. The process is quite simple - I tag and push. :-)

[bbatsov]

clojure-mode 5.1 is out!

[cap10morgan]

@bbatsov I pushed that other commit you mentioned to cider-nrepl, but I haven't had a chance to test everything yet.

[bbatsov]

OK, let me know when get to doing this.

We'll probably add #1502 to 0.10.1 as well.

[cap10morgan]

@bbatsov I don't personally use paredit (smartparens instead), so it might be good if someone else tested #1479.

[cap10morgan]

OK, all but #1479 and #1435 are tested and seem to be working in this branch.

[cap10morgan]

#1435 looks good.

[cap10morgan]

Actually, I think #1486 is not fixed in this branch. It's still broken in this screenshot, no? @jeffvalk?

Or maybe that's unrelated and the screenshot below is where the fix shows up?

[cap10morgan]

Should we fix #1503 before releasing v0.10.1?

[jeffvalk]

@cap10morgan #1486 is fixed in the screenshots above, yes.

[cap10morgan]

Pulling in a7e5671 fixed #1503.

I think the only thing left is to have a paredit user test #1479 and then we should be good to go.

[bbatsov]

I think the only thing left is to have a paredit user test #1479 and then we should be good to go.

That's working. :-)

[bbatsov]

I cut a new release, but it's probably broken due to an error in the middleware. The last commit backported there breaks the tests, but I noticed this too late and I didn't really have to investigate. I won't announce the release until we see what's wrong and I'll just swap the middleware jar.