Rhaboo has no tags/releases

[Download]

I noticed that you are not tagging/releasing your versions. I have forked your repo because of this, because I need version numbers to be able to serve Rhaboo off of RawGit CDN.

Do you have a reason not to make releases? It's actually a very simple process... You can make a release with a new tag in minutes...

[Download]

I made a fiddle for #33. When I refreshed that Fiddle, nothing changed. That's because it's pointing to a RawGit CDN version of Rhaboo... But it's pointing to master and never expires, so it does not pick up the changes. And I can't point it to a specific version.

I pulled in your changes into my fork and released from there. If you look at the new version of the fiddle, you can see that it now points to my fork.

Tagging your releases would really help. And it's a very straightforward process. Even I think it's easy! :)

If you are willing to give it a try and want some help, let me know. A great place to start is from within GitHub itself, on tab Releases there s a button Draft a new release. Just press it, fill in your version number as the tag, give the release a title and description and save. Voila, a new Git tag and Release within GitHub. And people can now reference that specific tag from within RawGit or e.g. Bower etc.

[adrianmay]

Oops. I saw this before but seem to have dropped the ball.

I'm not sure what you want here. Your HTML will refer to some URL with the rhaboo script. Do you want it to update as I make changes or not. If not, you could just host it yourself. If so, how about https://raw.githubusercontent.com/adrianmay/rhaboo/master/rhaboo.min.js

[Download]

What I would like is for you to visit the releases tab and press the button Draft a new release Then fill in the correct version number (and possibly some description etc and press 'Publish release'. Then, GitHub will tag the repo and make a source ZIP / tarball etc. After you have done that, we will be able to reference a specific version of Rhaboo using RawGit CDN.

Do you want it to update as I make changes or not.

No :) This is one of the reasons you should never link directly to a master version... The website would update live whenever a change was made here... Not recommended for production websites :)

If not, you could just host it yourself.

Yes that's possible, but it has a lot of downsides such as extra traffic to my website and much less chance that the file will already be in the user's cache.

RawGit is a fantastic service that automatically mirrors everything on GitHub in a CDN. But they only allow you to link to master copies for testing purposes:

For sharing low-traffic, temporary examples or demos with small numbers of people. Excessive traffic may lead to throttling and blacklisting.

They recommend people to create a tag (e.g. 'release' in GitHub terminology) and refer to that:

For use on production websites with any amount of traffic. Files are served via MaxCDN's super fast global CDN. No traffic limits or throttling. It's best to use a specific tag or commit hash in the URL (not a branch). Files are cached permanently after the first request.

So this is what I am asking you to do: Tag your releases so we can link to a specific version. GitHub makes this very easy.

Once you do this (which, again only takes a few minutes), we can include your script using URLs that look like this:

https://cdn.rawgit.com/adrianmay/rhaboo/3.2.4/rhaboo.min.js

[Download]

At the risk of boring you, let me give you one extra reason for preferring tagged releases (maybe the reason): Caching.

Have a look at this article: Best Practices for Speeding Up Your Web Site, in it they spend quite some time convincing us to use a CDN. Why? Because CDN's tend to be co-located (so available in Europe, east-coast, west-coast etc) and have caching headers set to never expire. Also, because the CDN is on a different host than the website itself, the browser will allow more than the usual amount of 2..6 max. concurrent requests... All in all using CDN's wisely can be a HUGE difference in performance for the end-user... at a lower cost because most CDN's are free and you are actually saving bandwidth to your own host.

[adrianmay]

Ok, you talked me into it. Maybe I get a chance tonight.

[Download]

Cool!