Updates to Versioning Engine

Mike's Notes

This week's changes to the Versioning Engine (ver).

Resources

References

  • Reference

Repository

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

Last Updated

16/10/2025

Updates to Versioning Engine

By: Mike Peters
On a Sandy Beach: 16/10/2025

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

The recent UI workspaces work necessitated changes to Pipi's Versioning Engine (ver). That engine's data model was changed.

Objects that can change

  • Industry models
  • Industry Schema
  • Workspace UI's
  • User training material
  • Developer Documentation
  • Etc

Versioned namespaces

Every object has a versioned namespace. When a logged change to an object occurs, the Pipi Build Number increments.

On any day, if there is one or more changes to the Build Number, the daily Patch Release automatically increases by 1. The changes are then published in the Changelog.

Minor Release

On the second Friday of every third month, the Minor Release increases by 1. A big picture summary of the preceding three months is published in the Changelog.

Objects in sync

Changes to the workspace UI, developer documentation, user training materials, and related materials need to be kept in sync.

DevOps

Making sure that the recently added DevOps Engine (dvp) runs this sync process might work. It could be done using workflows.

Summary

The engines involved are 

  • Versioning
  • DevOps
  • Learning Object
  • Workspace
  • CMS

No comments:

Post a Comment