That's unfair. Consider, hypothetically, a case where there is publicity on a subject that a Matasano employee has specific expertise about but which is also not orthogonal to Matasano's commercial interests. You can stipulate, if it helps, that the hypothetical employee is younger or less senior in the organization. They might reasonably decide to post something about that thing on HN or Twitter, and then follow it up with an out-of-an-abundance-of-caution disclaimer to head off any trouble at the office, right? That isn't double-secret-squirrel drama seeking, that's just trying to adapt to the weirdness of life as an employed social animal in 2013, where you have an ingroup-you and a public-you and occasionally they have to be both present in a conversation at the same time at cross-purposes to each other.

I'm sorry if you thought this was 'drama,' just trying to make sure that someone doesn't think that this is officially supported by the Rails team or that I'm speaking for anyone. Frankly, I've been running around at Ruby conferences saying "If you want old versions of Rails supported, you should be paying someone to do it," and I think Rails LTS is great, in a personal capacity.

That said, since I posted this, https://twitter.com/rails/status/346671286149337088