Clojurians Log v2

@rhu So I did that and my immediate reaction was that that might be a bad idea

because we have outstanding PRs

so now junit xml support doesn’t merge cleanly, prelim boot support doesn’t, and neither does the for loop chunked seq thing

any preferences moving forward? I’d like to get those in somehow, ideally without asking the contributors to do even more work

I don't mind mopping up the merge conflicts

Only this one is squealing about merge conflcts though: https://github.com/cloverage/cloverage/pull/127

Presume you'll need to give me write access do that though ?

Yeah, I’m happy to give you write access but I’m not sure how that’ll help

thought maintainers could now edit PRs ?

I can edit the title, but not the source branch

the loop chunked PR will merge cleanly but will fail travis because of the formatting rules,

Boot support will merge cleanly and travis passes

junit support has some merge conflicts

I mean, you could pull the branch and open a new PR

that is what I understood the procedure to always be for GitHub

how close do you think those PRs are to be merged into master?

when I said give me write access, i would’ve checked out locally, fixed the conflicts then pushed to master

but if the PRs are not quite ready, theres not point in doing that

I think they’re good to go

I just wanted a release I can trust

due to the lack of releases, a lot of people are running -SNAPSHOT

and some of these changes are benign, but the :for one might actually break something