Skip to content

Conversation

tbrisker
Copy link
Contributor

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 56.364% when pulling 62c827d on tbrisker:ruby193 into 82a3bc6 on fog:master.

@geemus
Copy link
Member

geemus commented Jan 17, 2017

Thanks, we should do this, but not quite ready to pull the trigger...

Also, looks like this may now be in conflict with the other changes we merged from you. Could you take a look? Thanks!

@tbrisker
Copy link
Contributor Author

@geemus thanks, updated.
I suggest creating a 0.1.3 release with the latest commits that will support 1.8 for those who still need it and making this a 0.2.0 release for those who don't. If there are bugs that are important or easy to pull back into the 0.1 branch you could have further releases on the 0.1 branch.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 56.364% when pulling a49e496 on tbrisker:ruby193 into 45cd8db on fog:master.

@geemus
Copy link
Member

geemus commented Jan 20, 2017

@tbrisker yeah, that could work. I am a bit bandwidth constrained currently, but when I'm ready to pull the trigger that sounds like a good approach.

@tbrisker
Copy link
Contributor Author

closed in favor of #11

@tbrisker tbrisker closed this Oct 29, 2017
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