Table of Contents

Jiro.Shared Release Code Names

This document contains the code naming convention and reference for Jiro.Shared releases.

Code Naming Theme

Jiro.Shared 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
v1.3.2 Seisō 整理 Organization/Cleanup Clean Logging Optimization
v1.3.1 Seigō 精確 Precision/Accuracy Serialization Fixes & Enhanced Logging
v1.3.0 Ōtō 応答 Response/Acknowledgment ActionResult & Response Pattern
v1.2.2 Tsuiseki 追跡 Tracking/Tracing Stream Request Tracking
v1.2.1 Bunri 分離 Separation Method Organization
v1.2.0 Nagare 流れ Flow/Stream Streaming Infrastructure
v1.1.6 Shinpo 進歩 Progress & Advancement Continued Improvements
v1.1.5 Kiban 基盤 Foundation Client Base Class & Event Wiring
v1.1.4 Chōwa 調和 Harmony Interface Naming Clarity
v1.1.3 Kizen 基盤 Foundation Refinement Model Enhancement & API Consistency
v1.1.2 Shinpo 進歩 Progress & Advancement Documentation & Testing
v1.1.1 Byakko 白虎 White Tiger Response Handlers & SignalR
v1.1.0 Kaizen 改善 Continuous Improvement Enhancement & Extension
v1.0.0 Hajimari 始まり Beginning Initial Release & Foundation

Future Code Name Ideas

For future reference, here are potential code names for upcoming releases:

Minor Releases (v1.x.x)

  • Shinpo (進歩) - "Progress & Advancement" - for enhanced features and capabilities
  • Kizen (基盤) - "Foundation" - for infrastructure improvements
  • Yūki (勇気) - "Courage" - for bold new features
  • Chikara (力) - "Power/Strength" - for performance improvements

Major Releases (v2.x.x+)

  • Shinseiki (新世紀) - "New Era" - for paradigm shifts
  • Kakushin (革新) - "Innovation" - for breakthrough changes
  • Takumi (匠) - "Artisan/Craftsman" - for refined, polished releases
  • Mirai (未来) - "Future" - for forward-looking, modern releases
  • Chōwa (調和) - "Harmony" - for integration and compatibility releases
  • Chōten (頂点) - "Peak/Summit" - for performance and optimization releases
  • Hatsumeika (発明家) - "Inventor" - for innovative features
  • Kanzen (完全) - "Perfection" - for feature-complete releases
  • Rinkaku (輪郭) - "Outline/Definition" - for API standardization
  • Kesshō (結晶) - "Crystal" - for clarity and precision improvements

Guidelines

When choosing a code name for a new release:

  1. Consider the Theme: What is the main focus of this release?
  2. Check Cultural Accuracy: Ensure proper understanding of Japanese terms
  3. Maintain Consistency: Follow the established pattern and style
  4. Document Meaning: Always include both Japanese characters and English meaning
  5. 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")