Originally created by @DoCode on GitHub (Jun 15, 2013).
I hope we can discuss it here...
Greets
Originally created by @DoCode on GitHub (Jun 15, 2013).

I hope we can discuss it here...
Greets
Could you add a question or an explanation? I have no idea what your point is, and judging from the number of comments so far, neither is anybody else.
@tbull commented on GitHub (Jun 23, 2013):
Could you add a question or an explanation? I have no idea what your point is, and judging from the number of comments so far, neither is anybody else.
@DoCode, I agree with @tbull, your table doesn't make any sense to me either. Since this issue will not result in a PR and nobody else seems to have engaged on this issue, please close it at your earliest possible convenience.
@jwdonahue commented on GitHub (Dec 2, 2017):
@DoCode, I agree with @tbull, your table doesn't make any sense to me either. Since this issue will not result in a PR and nobody else seems to have engaged on this issue, please close it at your earliest possible convenience.
Why do you not just close the issue in order to get rid of it? SEMVER is not about CI or defining any kind of process, it is an utility for making defined processes happen.
@silkentrance commented on GitHub (Dec 7, 2017):
Why do you not just close the issue in order to get rid of it? SEMVER is not about CI or defining any kind of process, it is an utility for making defined processes happen.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DoCode on GitHub (Jun 15, 2013).
I hope we can discuss it here...
Greets
@tbull commented on GitHub (Jun 23, 2013):
Could you add a question or an explanation? I have no idea what your point is, and judging from the number of comments so far, neither is anybody else.
@jwdonahue commented on GitHub (Dec 2, 2017):
@DoCode, I agree with @tbull, your table doesn't make any sense to me either. Since this issue will not result in a PR and nobody else seems to have engaged on this issue, please close it at your earliest possible convenience.
@silkentrance commented on GitHub (Dec 7, 2017):
Why do you not just close the issue in order to get rid of it? SEMVER is not about CI or defining any kind of process, it is an utility for making defined processes happen.
@jwdonahue commented on GitHub (Jul 15, 2018):
@DoCode, please close this issue at your earliest possible convenience. Thank you.
@DoCode commented on GitHub (Jul 15, 2018):
Closed by design