Well, I must confess when I first agreed to take over maintenance of this plugin I wasn’t prepared for just how burned out I’d gotten at the time, so while I did manage to get 3.3.7 out the door, I have to admit progress was far slower than I would’ve liked.

But, version 4.0.0 is finally done, and I’ve managed to integrate a bunch of changes I had queued up while dealing with a bunch of open issues in the tracker.

Here’s hoping I didn’t break anything horribly (I dogfood the main branch on my own blog but I’m not going to claim that exercises every corner of the codebase, and I’ve not begun the monumental effort to close out issue #29, so automated tests are still very much absent).

With that said, version 4.0.0 of this plugin brings along a couple of major new features, along with some more minor enhancements. While the gem behaviour and associated configuration should be backward compatible with the 3.x series, the changes are significant enough that I felt it best to bump the major version of the plugin so folks are less likely to experience a surprise upgrade.

This is a copy of the note I posted to LinkedIn announcing my resignation from INVIDI. Since I didn’t syndicate my last blog post there, you’ll forgive a bit of overlap in the subject matter, but I liked what I wrote and wanted to preserve it on my blog. You know, Own Your Data and all that.

The beginning

Twenty-one years.

For many of the folks I know, twenty-one years is a long time in a career, let alone in a single company.

But the strange thing is that, while on the resume it looks like I’ve had just the one job, in reality I had the great fortune to have experienced a remarkably diverse series of roles, and it seemed like every time I started to get a little antsy, a little bored, in need of a change, INVIDI offered me another opportunity, another challenge, another path to walk.

And it has been quite the journey, though one that has come to its natural end.