=> https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12%E2%80%93semver.txt
3=> https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12%E2%80%93semver.txt
3=> https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12%E2%80%93semver.txt
3'/phlog/2022-02/2022-02-12\\M-b\\M^@\\M^Ssemver.txt'
Clearly wrong. Looks like some clever software took over and replaced the two ASCII hyphens (0x2D) with a Unicode En Dash (U+2013). See the URL you linked:
ā¦ 2-02-12%E2%80%93semv ā¦. That %E2%80%93 shouldnāt be there.Works:
https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12--semver.txt
'/phlog/2022-02/2022-02-12\M-b\M^@\M^Ssemver.txt'
Clearly wrong. Looks like some clever software took over and replaced the two ASCII hyphens (0x2D) with a Unicode En Dash (U+2013). See the URL you linked:
ā¦ 2-02-12%E2%80%93semv ā¦. That %E2%80%93 shouldnāt be there.Works:
https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12--semver.txt
'/phlog/2022-02/2022-02-12\M-b\M^@\M^Ssemver.txt'
Clearly wrong. Looks like some clever software took over and replaced the two ASCII hyphens (0x2D) with a Unicode En Dash (U+2013). See the URL you linked:
ā¦ 2-02-12%E2%80%93semv ā¦. That %E2%80%93 shouldnāt be there.Works:
https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12--semver.txt
'/phlog/2022-02/2022-02-12\M-b\M^@\M^Ssemver.txt'
Clearly wrong. Looks like some clever software took over and replaced the two ASCII hyphens (0x2D) with a Unicode En Dash (U+2013). See the URL you linked:
ā¦ 2-02-12%E2%80%93semv ā¦. That %E2%80%93 shouldnāt be there.Works:
https://gopher.mills.io/uninformativ.de/0/phlog/2022-02/2022-02-12--semver.txt
Having said that, I'm not sure if I would change from date-based to semantic versioning. Another think coming to mind: Starting semver with a major version of 2022 or 22 (so that the new versioning scheme doesn't start lower than the old scheme) looks rather weird to me. I don't write browsers. ;-)
But you stroke a nerve. I should write changelogs. Because currently I don't. Which changelog standard to you use?
So I think I'm not very helpful here. Sorry. :-(
By the way, since I didnāt pay *too much* attention to not introduce breaking changes, some of my tools would have (almost) reached version 23 by now anyway. š„“
No worries, your comment was actually very helpful. Hereās what I originally had in mind: āHmm, my existing releases are called like
v21.01, so I could just drop the v and start with 1.0.0 for everything.ā In retrospect, thatās super braindead. š¤¦ Just going for 23 makes much more sense. Sometimes, Iām not a smart person.As for changelogs: Thereās https://keepachangelog.com/en/1.0.0/. This is a huge discussion in itself, by the way (see here, for example). *Changelogs* donāt make sense anymore, since basically everything uses a version control system these days. What you might want to write is a *news* file, which doesnāt list every single commit or change, but rather: Important stuff that people should be aware of. And you have the problem of āreservedā names like
NEWS (https://www.gnu.org/prep/standards/html_node/NEWS-File.html), which should then probably follow a certain file format or whatever.I went for a slightly modified version of CPAN CHANGES. Thereās always a section āFixedā, āChangedā, āAddedā in my files, because I think itās very important that the reader immediately knows what kind of change weāre talking about. (And I didnāt quite like the Markdown noise in keepachangelog.com.)
By the way, since I didnāt pay *too much* attention to not introduce breaking changes, some of my tools would have (almost) reached version 23 by now anyway. š„“
No worries, your comment was actually very helpful. Hereās what I originally had in mind: āHmm, my existing releases are called like
v21.01, so I could just drop the v and start with 1.0.0 for everything.ā In retrospect, thatās super braindead. š¤¦ Just going for 23 makes much more sense. Sometimes, Iām not a smart person.As for changelogs: Thereās https://keepachangelog.com/en/1.0.0/. This is a huge discussion in itself, by the way (see here, for example). *Changelogs* donāt make sense anymore, since basically everything uses a version control system these days. What you might want to write is a *news* file, which doesnāt list every single commit or change, but rather: Important stuff that people should be aware of. And you have the problem of āreservedā names like
NEWS (https://www.gnu.org/prep/standards/html_node/NEWS-File.html), which should then probably follow a certain file format or whatever.I went for a slightly modified version of CPAN CHANGES. Thereās always a section āFixedā, āChangedā, āAddedā in my files, because I think itās very important that the reader immediately knows what kind of change weāre talking about. (And I didnāt quite like the Markdown noise in keepachangelog.com.)
By the way, since I didnāt pay *too much* attention to not introduce breaking changes, some of my tools would have (almost) reached version 23 by now anyway. š„“
No worries, your comment was actually very helpful. Hereās what I originally had in mind: āHmm, my existing releases are called like
v21.01, so I could just drop the v and start with 1.0.0 for everything.ā In retrospect, thatās super braindead. š¤¦ Just going for 23 makes much more sense. Sometimes, Iām not a smart person.As for changelogs: Thereās https://keepachangelog.com/en/1.0.0/. This is a huge discussion in itself, by the way (see here, for example). *Changelogs* donāt make sense anymore, since basically everything uses a version control system these days. What you might want to write is a *news* file, which doesnāt list every single commit or change, but rather: Important stuff that people should be aware of. And you have the problem of āreservedā names like
NEWS (https://www.gnu.org/prep/standards/html_node/NEWS-File.html), which should then probably follow a certain file format or whatever.I went for a slightly modified version of CPAN CHANGES. Thereās always a section āFixedā, āChangedā, āAddedā in my files, because I think itās very important that the reader immediately knows what kind of change weāre talking about. (And I didnāt quite like the Markdown noise in keepachangelog.com.)