Skip to content

Conversation

trollfred
Copy link

No description provided.

@tmcgilchrist
Copy link

Seems like this is needed before we'll get passing builds on the other PRs.
I'm wondering if it needs to include all 3 released versions of 17? Perhaps just the latest one is sufficient.

@jlouis

@jlouis
Copy link
Collaborator

jlouis commented Dec 15, 2014

I'm not really maintaining this project anymore. Garrett Smith has volunteered to carry the baton, so you would have to address him instead, and perhaps go looking at his fork. As for the 17.x releases, I think supporting 17.4 and 16B03 should be enough. Essentially, support the latest patch release of the previous version of Erlang, and support the current latest patch-release. But YMMV. For Emysql, it may make sense to support more versions. In any case, it isn't really my call to make.

@trollfred
Copy link
Author

@gar1t what do you think of it?

@tmcgilchrist
Copy link

Apologies @jlouis I didn't see who actually took over maintaining this library in the erlang-questions mailing list. As I said I'd like to help out around here so I'll hit up @gar1t in future. Cheers.

@jlouis
Copy link
Collaborator

jlouis commented Dec 15, 2014

No problem. It was a recent development and only announced on the erlang-questions@ mailing list, so you couldn't possibly have known in any case. I just want to help out where possible with a maintenance transition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants