Update CHANGELOG for 4.0.2

Question

Update CHANGELOG for 4.0.2

Closed this issue 9 years ago · 6 comments

PikachuEXE commented 9 years ago

<= Too busy to read all commits

Answer 1 · 2015-08-17T02:29:34.000Z

I think per semantic versioning this should've been 4.1.0 actually (additive API change)

Answer 2 · 2015-08-17T03:25:59.000Z

Noted. Yank and recut, or rejoin semver at 4.1.* next release?

Answer 3 · 2015-08-17T03:35:22.000Z

Should it be yanked due to invalid version?
I really have no idea :S

Answer 4 · 2015-08-17T04:20:50.000Z

Well, @tarcieri is right.. and this gem doesn't release that frequently -- as it shouldn't. So it should really keep to semver rather than anticipate a future release to catch up with.

I notice that last year 3.0.1 and 4.0.0 were released the same day, adhering to semver... so with that precedent I am going to yank and recut at 4.1.0 ... at the changelog update.

Answer 5 · 2015-08-17T04:23:40.000Z

Edit: Released a month apart, not same day. Just happened to be same day number in each month and I misread as same day. Either way.

Answer 6 · 2015-08-17T04:36:44.000Z

Recut at 4.1.0 with changelog.