...
Timma releases every Thursday. Each release gets its own page listing what changed, in plain language.
Each weekly page is split into three parts, because "we shipped it" and "a salon can tell" are not the same thing:
Section | What goes in it |
|---|---|
Highlights | Features that reached more customers than the week before, plus the two or three biggest items. Read this if you read nothing else. |
Changes your customers will notice | Changes to features salons are already using, so the difference is visible straight away. This is the section support and sales need. |
Everything else | Collapsed. Groundwork on features that have not launched, plus internal and commercial work. Nothing here changes anything for a salon this week. |
The split between the last two sections follows the feature's status above: work on something still In development cannot be customer-visible, because the feature is not out yet. That is why a week's biggest body of work sometimes sits in the collapsed section.
| Expand | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
These are long since live and stable. They are kept out of the table above so it only shows what is changing.
|
...
Everything finished that week is stamped with the week's release version in Jira.
A new weekly page is written from that list and added under the current year.
The table above is regenerated.
The release is marked as released in Jira and the board is cleared.
Tickets that matter to customers, support or sales worth mentioning at all are tagged SLIDES in Jira. Those become the visible sections of the weekly page; everything else goes under "Behind the scenes" so the page stays readable without hiding anythingThat tag decides whether an item appears; the feature's status decides which of the three sections it lands in.
| Warning | ||
|---|---|---|
| ||
A feature's status cannot be read off a Jira workflow or off the code. Epics sit in "In Progress" for months after a feature is live, and the step that switches a feature on for every existing salon is often run straight against the production database, leaving no trace anywhere. So each epic carries an explicit label — |
...