New rubygem release

[mdurn]

I was wondering if there could be a new rubygem release since there have been a good amount of changes since the last release. I'm fine using the commit sha for now, but it would be handy.

Thanks!

[jackphelps]

At least another version bump; I just spent a really long time banging my head against the wall with the old gem because the repo didn't show any version changes; didn't realize how much it had changed.

[jkrall]

Yep, sorry guys. I'll try to push a new one out by end-of-week. (I'm swamped today and travelling all day tomorrow). Maybe one of the other collaborators will have time between now & then.

I'm hoping to take a more active role in maintaining this gem in the future. For the past year+ its been hard to find time because of my work situation, but that's changing a bit.

[jackphelps]

for the record, it seems really useful, I appreciate the work

[sfsekaran]

Perhaps I can take a look soon.

On Wednesday, July 30, 2014, Jack Phelps notifications@github.com wrote:

for the record, it seems really useful, I appreciate the work

—
Reply to this email directly or view it on GitHub
#82 (comment).

[fabn]

+1 for this

[mcnasby]

Would also love a version bump. Starting to use this gem more and plan on developing a couple additional modules for it -- already have a Google Tag Manager module in the works.

[mandrews]

+1 for new release

[nj]

+1 as latest official release was on January 24th, 2012 !

[jkrall]

I haven't been using this in production in quite a while (though many other people are, I believe)... can anyone chime in on the stability of the current master?

Happy to cut a new release, but I don't want to break anything for anyone. I guess I could bump the minor version at least. Thoughts?

[infertux]

👍 for a new release @jkrall

I haven't used the version from master much so I can't comment on the stability of it.

However, the README on GitHub is full of examples which don't work with the old version from 2012, which is confusing for new users of the Gem.

If you don't know whether there has been changes that will break backward compatibility, may I suggest you push a new major version to Rubygems.org, like 4.0.0? That way, people will be careful about updating and you won't break anything for anyone as per semantic versioning. I'm sure a lot of people would appreciate not having to use the Git version of the Gem 😄

[mdurn]

I'm only one commit behind (so I don't have google universal fix: e13e361). I've been using it for Mixpanel and it has been working fine for me. The current gem release had an old version of the mixpanel js and I needed the new one. So people could potentially have an issue if they are using the old js library anywhere.