Pipi 9.1.0

Mike's Notes

Pipi self-versioning has resumed after being frozen since 2020. Previously, Pipi was versioned whenever developers logged changes.

Resources 

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

10/01/2026

Pipi 9.1.0

By: Mike Peters
On a Sandy Beach: 9/01/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Automated Pipi semantic versioning has restarted. The previous version was frozen at Pipi 9.0.2+398; the current version is Pipi 9.1.0+399.

The next minor version change occurs on Friday, 10 April 2026, at 8am.

Build

  • Every change to a namespaced object increments the Build Number by 1
  • It is the internal system change ID
  • Daily Builds could vary from 0 to 1,000s
  • 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 at 8am, NZ Time.
  • 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

Notes

Minor releases account for emergent behaviour changes in the system as a whole; the date is arbitrary. Major Releases account for phase-level changes when they occur.

It will take a while to get everything running according to plan. It requires enabling extensive automation across multiple systems. As a result, some parts will initially be out of sync.

If the Version Engine (ver) had been running since 2000, the number of changes would make the current Pipi version look something like

  • Pipi 9.18.78+25,000-beta

Rendered HTML

Rendered: 08:41 UTC, 9 January 2026 by Pipi 9.1.0+399-beta

No comments:

Post a Comment