Jiro.Libs Release Code Names
This document contains the code naming convention and reference for Jiro.Libs releases.
Code Naming Theme
Jiro.Libs uses Japanese-inspired code names that reflect the spirit and theme of each major release. The names are chosen to be:
- Meaningful: Reflecting the key improvements or theme of the release
- Memorable: Easy to remember and reference
- Cultural: Inspired by Japanese concepts and philosophy
Release History
Version | Code Name | Japanese | Meaning | Theme |
---|---|---|---|---|
v2.0.0 | Kaizen | 改善 | Continuous Improvement | Foundation & Initial Framework |
v3.0.0 | Shinpo | 進歩 | Progress & Advancement | Enhanced Tooling & Documentation |
v3.0.1 | Shinpo-Kai | 進歩改 | Enhanced Progress | Release Process Automation |
v3.0.2 | Kaizen-ka | 改善化 | Improvement Process | Incremental Improvements & Bug Fixes |
v3.0.3 | Seishin | 精神 | Spirit & Essence | Core Framework Strengthening |
Future Code Name Ideas
For future reference, here are potential code names for upcoming releases:
Minor Releases (v3.x.x)
- Kaizen-ka (改善化) - "Improvement Process" - for incremental improvements
- Seishin (精神) - "Spirit/Essence" - for core feature enhancements
Major Releases (v4.x.x+)
- Hatsumeika (発明家) - "Inventor" - for innovative features
- Kakushin (革新) - "Innovation" - for breakthrough changes
- Takumi (匠) - "Artisan/Craftsman" - for refined, polished releases
- Mirai (未来) - "Future" - for forward-looking, modern releases
- Harmony (調和) - "Harmony" - for integration and compatibility releases
- Zenith (頂点) - "Peak/Summit" - for performance and optimization releases
Guidelines
When choosing a code name for a new release:
- Consider the Theme: What is the main focus of this release?
- Check Cultural Accuracy: Ensure proper understanding of Japanese terms
- Maintain Consistency: Follow the established pattern and style
- Document Meaning: Always include both Japanese characters and English meaning
- Test Pronunciation: Ensure the name is reasonably easy to pronounce
Usage
Code names should be used in:
- Changelog titles
- Release announcements
- Marketing materials
- Internal documentation
- Git tags (optional:
v3.0.0-shinpo
)
The code name appears in the format: Version "CodeName"
(e.g., v3.0.0 "Shinpo"
)