Merb '1.1.0' is a typo and causing problems for people trying to get on edge
Correct me if I am wrong, but installing merb via "sudo gem install merb --source http://edge.merbivore.com" installs merb version 1.1.0. This is incorrect. There is not yet a 1.1.0 version.
I believe it is at typo and should be 1.0.1 released on Nov 18th. see http://wiki.merbivore.com/
The bad problem with this is that the combination of different install options will likely cause a newbie trying to get on edge some issues. If they install on edge via a github clone and rake install they will get version 1.0.3 or soon 1.0.4 (tagged this afternoon), but if they install from the supposedly 'EDGE.merbivore.com' they are not actually getting edge.
I actually vote to remove the install option via edge.merbivore.com. It is confusing and unnecessary. Let those who want to install edge do so from the github repo and those who don't just install with sudo gem install merb.
Sorry for the long post.
Comments and changes to this ticket
- State changed from unconfirmed to invalid
It's not a typo as so far always was this way: HEAD has the next release version on the branch. Making it 1.1.0-dev or something complicates release process and is error prone (we've done it prior to 0.9.3 or so I guess).
I don't think that is correct Michael (but granted I'm way out of my league here) based on the documentation page - http://merbivore.com/documentati...>
Why then would there be a HEAD and a 1.1.0 api generated nightly?
Furthermore, as I understand the master branch is HEAD, correct? However, the master branch is almost a month behind the 1.0.x branch. Therefore, by pulling HEAD (1.1.0) you are actually getting an older version of merb.