-
Notifications
You must be signed in to change notification settings - Fork 2
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
Everyone using the same version? #3
Comments
Couldn't you check out tag 1.3.2 into a new branch and push that to our sinatra repo? That way you could set it as the default. |
aha! why didnt i think of that! On Thu, May 31, 2012 at 10:02 PM, Andreas Arnold <
|
@Zumda Done. I created a new branch from the tag v1.3.2 and named it ver1.3.2 . It has been set as the default branch in github. |
I am meaning to do a 1.3.3 release really soon, but it's just minor bug fixes. |
@codereading/readers
The latest gem release is version 1.3.2 however the master branch, I think, is 5 months ahead of that. So if everyone is fine with this version remember to clone the repository and checkout to the tag 1.3.2 for your codereading pleasure! Or you could just
gem unpack sinatra
Also the file viewer in github will show the master branches files. So there will be differences. Unfortunately github only allows me to set a branch as a default for the project and not a tag. Sinatra does have a 1.3.x branch but that seems to include all commits uptill now and untill 1.4.x. So I have left it at master.
The text was updated successfully, but these errors were encountered: