Don’t worry, you can keep your current plan for the foreseeable future
Those who have been with Reviewable for a long time may have noticed that we never (ever!) updated our prices in the 9 or so years we’ve been around. Look, don’t judge us -— we’re engineers, we’d rather be shipping cool new features than messing around with spreadsheets. Nonetheless, all those new features add up . . .
It didn't "SOC2 much", as the obligatory pun goes
As some of you may know, we've been working on getting a SOC 2, and we're excited to announce that as of last week we have completed our "System and Organization Controls 2" (SOC 2) Type I audit! If you'd like to get a copy of it, please reach out to firstname.lastname@example.org and we'd be happy to share it.
. . .
Let's walk through the life of a code review together, and while we do so I'd like to show you two ways to view that lifecycle.
A junior dev, Bob, pulls the main branch (formerly known as the master branch) and creates his own branch, at commit
Bob$ git pull Bob$ git checkout -b bob/featureBob Bob$ git . . .
We're going to switch to monthly posts, mainly to reduce my workload! As a result, these changelogs will include a lot of changes you've already been able to see for a while, and a few changes from the last week.
We'll also be skipping the smaller tweaks and bug fixes, so these posts don't become enormous. Otherwise, these would be pages . . .
Mostly bug fixes this time around. I could avoid this awkwardness by posting only next week, but I'm going to face the awkwardness and ... hi there ...
Code Review Experience
We fixed an issue that not warn you about a draft being open when closing a tab. Browsers sometimes change how this works, and it seems newer ones only allow
. . .
We just released our May Enterprise release, if you would like more information about that visit our or contact us at
As a result, the work mentioned in this changelog is mainly initial work for larger changes, and a bunch of small bug fixes.