Advance objective c version to v1.0.2#8871
Conversation
|
Might the rest of the project ever want to release 1.0.2? |
|
No, this is just an Objective C release |
|
@jcanizales Ping :) Need it soon. |
|
This is just an Objective C release alright, but that doesn't answer my question :) I'm trying to avoid the following scenario: The rest of gRPC goes to 1.0.2 to fix some security bug four months from now. Now Objective-C can't update to the 1.0.2 version number because that number's already taken by this podspec. Mess. |
|
From what I got from Kailash other languages go to v1.0.3 next. @nicolasnoble can you confirm how it works? |
That'd solve my worry. |
jcanizales
left a comment
There was a problem hiding this comment.
Think about getting the actual version number from the common source, like the other languages, so it's much easier to be sure that it's been changed in all the necessary places.
|
re version bumps, http://semver.org/ does not dictate the steps of the increment, only that there must be increments, so all other languages can skip 1.0.2 and go to 1.0.3.. this is my understanding. Doing this reduces unnecessary churn for users of other languages since they do not have to deal with a NOOP version bump. |
To use Objective C only tag "objective-c-v1.0.2"
cc: @nicolasnoble @hsaliak