https://twyne.samwilson.id.au/T152Fri, 07 Aug 2026 18:42:33 +0000<p>It’s Wednesday morning, coffee is made, and <a href="https://svgtranslate.toolforge.org/">SVG Translate</a> is being upgraded to 2.0.0. I think that bumping major version numbers for underlying platform upgrades is slightly controversial, but I do it. My reasoning is that a major version primarily indicates that “something” must be done when you upgrade, and that’s definitely true when dropping support for old versions of PHP.</p> <p>A few of the tools that use the <a href="https://github.com/wikimedia/ToolforgeBundle">ToolforgeBundle</a> for Symfony display their current version number in the footer, and they do so by running <code>git describe</code> to get the current tag. This is proving to be silly when the filesystem is slow, and is timing out. It’d be better to have the current version number within the codebase somewhere — the trouble with that is remembering to keep it in sync. Ideally, I think, it’d be in a <code>VERSION</code> file, and would get updated every time a change is made so that there’s only ever one commit with a given version (other than <code>-dev</code> ones; i.e. the next commit after a release would add that).</p>https://twyne.samwilson.id.au/P26707https://twyne.samwilson.id.au/P26707Wed, 06 Mar 2024 01:37:00 +0000<p>I thought it’d be a simple matter to update SVG Translate’s i18n messages, but no <em>of course</em> if I’ve not touched a thing for a few months it’s going to break. Not that I’ve changed anything, of course, but the gremlins must have…</p>https://twyne.samwilson.id.au/P166https://twyne.samwilson.id.au/P166Fri, 12 Feb 2021 00:45:24 +0000