TwUI: Add pod for released versions 0.1-0.4

[jerolimov]

And drop support for random commit version 0.0.1!

Current (and now removed) version 0.0.1 points to this "random" (?) commit:

• 0.0.1: github/twui@0d03e1a

I've added release versions for 0.1 - 0.4 to two matching commit refs and two tags:

• 0.1: github/twui@2a704ca
• 0.2: github/twui@ef55cfc
• 0.3: https://github.com/github/twui/tree/0.3.0
• 0.4: https://github.com/github/twui/tree/0.4.0

[travisbot]

This pull request passes (merged 123a0f9 into c51614d).

[fabiopelosin]

And drop support for random commit version 0.0.1!

When a library is unversioned and somebody wants to add it to CocoaPods it uses the lasted reference and marks it as 0.0.1.

Please don't remove existing versions because we want a podfile to be as much reliable as possible (we want pod install give a Podfile and a Podfile.lock to produce the same results across different machines and time... we are not there yet). Although 0.0.1 might be an exception as it is unlikely that somebody requires them explicitly and they could be deleted but I think that this should be done after we create an issue a have a proper discussion about it.

Regarding 0.3 it points to a commit, but it should be a tag.

[travisbot]

This pull request passes (merged 753c886 into c51614d).

[jerolimov]

Fix v0.3

I think restoring v0.0.1 is not required because any user knows that a 0.0.1 is a unreleased version. So it works with ~> 0.0.1 and it clears that now (and in any future) the TwUI specs contains only releases.

Currently the 0.0.1 spec is anywhere between 0.2 and 0.3 and this doesn't show the version number which is imho more crappy than a removed version which requires (some few, if any) to update their (imho broken) dependency to .. i don't know ... the older 0.2 or the newer 0.3?

[fabiopelosin]

I think restoring v0.0.1 is not required because any user knows that a 0.0.1 is a unreleased version. So it works with ~> 0.0.1 and it clears that now (and in any future) the TwUI specs contains only releases.

One day we'll have to manage with outdated podspecs (move to separate repo?). In the meanwhile we usually keep them in order to not break existing podfiles.

Currently the 0.0.1 spec is anywhere between 0.2 and 0.3 and this doesn't show the version number which is imho more crappy than a removed version which requires (some few, if any) to update their (imho broken) dependency to .. i don't know ... the older 0.2 or the newer 0.3?

I didn't know about the inconsistency in this case I agree that it is better to remove it. I'm merging!