Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release a new version to rubygems #47

Closed
ktdreyer opened this issue Dec 26, 2013 · 6 comments
Closed

release a new version to rubygems #47

ktdreyer opened this issue Dec 26, 2013 · 6 comments

Comments

@ktdreyer
Copy link

Would you mind releasing a new version to rubygems.org, now that code for ActiveSupport 4 has been merged to master? It would be nice to have this fixed in an official version.

@ktdreyer
Copy link
Author

Hi Issac, Bram, Avdi,

Just a gentle ping to see if you could please tag and release a new version to rubygems?

This is affects the Fedora packaging, as well as the bogus gem (nulldb is in the dep chain for bogus.)

@blaet
Copy link

blaet commented Jan 17, 2014

@ktdreyer +1. Sadly I'm not a maintainer, but I have just mailed @isaacsanders and @myronmarston asking if I can assist in maintaining nulldb. Will keep you updated.

@erkki
Copy link

erkki commented Jan 18, 2014

Likewise +1 , just starting to look into nulldb on rails4+pg, happy to help in any way I can

@blaet
Copy link

blaet commented Feb 1, 2014

Released. Let's collaborate on database(pg)-specific support :)

@blaet blaet closed this as completed Feb 1, 2014
@ktdreyer
Copy link
Author

ktdreyer commented Feb 7, 2014

For the record, this was fixed with v0.3.0

@blaet
Copy link

blaet commented Feb 7, 2014

Indubitably, my dear @ktdreyer 🎩

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

No branches or pull requests

3 participants