Mike's Notes
The current work on building SaaS workspaces has raised the question of the Pipi release cadence. Documentation also has to be versioned. Then there is the monthly research newsletter. Here is a plan to use Fridays to create a rhythm of deadlines.
I was deeply influenced by writings from Shopify and Refactoring.
Resources
- https://semver.org/
- https://changelog.shopify.com/
- https://refactoring.fm/p/how-shopify-executes-editions
- https://www.shopify.com/editions/winter2025
- https://refactoring.fm/p/the-four-types-of-work-2023
- https://www.blog.ajabbi.com/2025/09/ajabbi-research-monthly-newsletter.html
- https://www.blog.ajabbi.com/p/pipi.html
- https://www.blog.ajabbi.com/2024/09/pipi-versioning.html
- https://handbook.ajabbi.com/eng/9/team/cadence.html
References
- Reference
Repository
- Home > Ajabbi Research > Library > Subscriptions > Refactoring
- Home > Handbook > Teams > Cadence
Last Updated
10/10/2025
Pipi release cadence
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
There have been thousands of changes to Pipi since version 9, but the official Pipi version is frozen till full automated self-management kicks in 2026. This is a description of what will happen then.
Pipi Versioning
Pipi uses Semantic Versioning <major>.<minor>.<patch>.<build>
Example
- 9.04.23.1453455072
Build
- Every change to a namespaced object increments the Build Number by 1
- Never resets.
Patch
- Release daily if there have been Build Number increases
- Numbered 0-999
- Resets when a Minor Release occurs
- Minor documentation edits
Minor Release
- Release 4x per year, 3 months apart on the 2nd Friday.
- Numbered 0-99
- Resets when a Major Release occurs
- Documentation officially updated
Major Release
- Release when a Minor Release backwards-incompatible change occurs, on the 2nd Friday of January, April, July or October.
- Usually every 2-3 years
- Numbered 1-99
- New documentation released
- Account migration required
On a Sandy Beach
- Published daily
- My notes on building Pipi, a self-organising platform to support critical infrastructure
Friday Report
- Published every Friday
- A summary of the week's work is sent to other researchers.
Research Newsletter
- Published 12x per year on the 1st Friday.
- Numbered 1-99999
- Dated by month and year, eg "January 2026"
- Named by theme, eg " Design Systems Issue"
Cadence
| Type | What | Date |
|---|---|---|
| Newsletter | Design System | 1st Friday, January |
| Release | 9.1.0 | 2nd Friday, January |
| Newsletter | i18n | 1st Friday, February |
| Newsletter | Open Handbook | 1st Friday, March |
| Newsletter | Complex Adaptive Systems | 1st Friday, April |
| Release | 9.2.0 | 2nd Friday, April |
| Newsletter | Origins of Pipi | 1st Friday, May |
| Newsletter | 1st Friday, June | |
| Newsletter | 1st Friday, July | |
| Release | 9.3.0 | 2nd Friday, July |
| Newsletter | 1st Friday, August | |
| Newsletter | 1st Friday, September | |
| Newsletter | 1st Friday, October | |
| Release | 9.4.0 | 2nd Friday, October |
| Newsletter | 1st Friday, November | |
| Newsletter | 1st Friday, December |
No comments:
Post a Comment