The pièce de résistance is Dist::Zilla::Plugin::NextVersion::Semantic which I had promised to Mike Doherty a long time ago. In a nutshell, the plugin examines the changes of the upcoming release and increases the version according to the rules of semantic versioning.
I’m in the throes of a major redesign of the site of my comic book, Académie des Chasseurs de Primes. Like any of those redesign, it involves a lot of CSS whack-a-mole. Fine-tuning one page throws a second one slightly off another, and fixing that second one causes unforseen effects on a third one. And so on, and so bloody forth. Generally, to discover those oopsies, I have to navigate the whole site. Bah, humbug. Wouldn’t it be much efficient to have a single document showing all of the site’s page? Something like a contact sheet for the website, if you will. Well, let’s see how hard that would be.
I have a Person class, and I want to know if they can pass the butter. So far, it’s hardly a problem,But here’s the rub. If $georges can’t pass the butter, I want to know why. Is it because he’s too far away, because there is no butter on the table, because he doesn’t like me, or any other reason? What is the most elegant way of knowing the if and the why?
What if I found a way to get the blog entries, and plop them on mailboxes on my mail server? That would take care of ubiquitous access. And since I would have control on the software, I could probably manage to filter out dupes. I sat down and began to hack on this. The result is mailfeed (clever project name pending). I’m still not sure if it’s a good idea, but at least its execution showcase how much niftiness can be crammed within 144 lines of code. But let me show you…
My first stab at SQLiteTAP is on GitHub. I’m writing it as a SQLite extension, so I had to brush up very rusty C skills. But after a few hours pouring over the documentation, and poking here and there, I have a working implementation of ‘plan’ and ‘ok’. Nothing earth-shattering, I’ll concede, but a nice start nonetheless.
As previously reported, last week-end’s activities could be summarized as me going to town on a yak herd with a lawnmower. And although the rest of Saturday and this morning haven’t been as fast and furious as Saturday morning, there’s a few more things to report:
So HP Cloud is finally yielding for some beta rain since their announcement late September. It started late September when I signed up for private beta testing. Two weeks ago, I got invited to join the beta and start testing the platform, here’s whats offered.
I’ve revived Perl::Achievements. I thought that would keep the wolves at bay, but noooo… Not a hour after the announcement was sent, I got a new feature request. I really should not but… okay, I wanted to do it anyway and if somebody is actually asking for it, why the heck not? Plus, it’ll give me the opportunity to see if my Template::Caribou is up to snuff. A few hours later, I have a bug report for MooseX::App::Cmd and (after some touch-ups) released the first version of Template::Caribou on CPAN.
Perl::Achievements is now on CPAN. The goal of the app is the same as presented in the original blog entry. I’ve, however, fleshed out a little bit more the documentation, tidied up the code a wee bit (well, it’s still a mess, but it’s using a lot of cool stuff, so it’s a shiny mess), and changed the innards just a tad. Wanna use it?
We have seen agile development become more popular in recent years thanks in part to the evolution of continuous integration environments like Ruby on Rails. These development frameworks leverage quick testing and the ability to easily deploy over clusters. As deployments happen more often, we look for ways to minimize the disruption to users. Cluster architecture already contains the components…