It’s Wednesday morning, coffee is made, and SVG Translate 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.

A few of the tools that use the ToolforgeBundle for Symfony display their current version number in the footer, and they do so by running git describe 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 VERSION 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 -dev ones; i.e. the next commit after a release would add that).

I’ve been wondering for a while how it’d be setting up a package on Packagist from Wikimedia’s GitLab… turns out it’s incredibly simple, and we now have wikimedia/toolforge-skeleton added and working! There’s still more to be done on it, but hopefully it’ll make it super quick to bootstrap the development of new PHP tools.

I’ve made a little Symfony tool for generating CLI usage documentation in Readme files: https://github.com/samwilson/console-readme-generator

So far I’ve not added it to many projects, but will do so. I mostly want to use it as a CI step to help keep Readme docs up to date with changes in Console commands.

Here’s an example of the output: https://github.com/wikimedia/ws-export/#cli-usage

It’s the middle of the morning here, but that doesn’t matter. I’m attempting to add tags to Twyne (I’d link that, but still haven’t implemented hyperlinks in my Sam-flavoured Markdown). It’s going fine, it’s not a complicated thing to do really, but I’m bumping skulls with Doctrine ORM. I’ve used it before for a couple of projects, but not for a while, and I’d forgotten how frustrating it is to be poking at DQL or a query builder and trying to make it work — when the equivalent SQL is simple and easy! I wouldn’t mind if this was something complicated, but ordering by the count of a joined table shouldn’t take an hour to figure out.