Skip to content

As a release manager, I want to ship marketplace 1.0 so that users receive the stable 1.0 milestone release #408

Description

@kiyotis

Situation

Current versions (all to be bumped to 1.0):

  • nabledge-6: 0.10 → 1.0
  • nabledge-5: 0.5 → 1.0
  • nabledge-1.4: 0.4 → 1.0
  • nabledge-1.3: 0.4 → 1.0
  • nabledge-1.2: 0.4 → 1.0
  • Marketplace: 0.11 → 1.0

No [Unreleased] entries exist; there are no functional changes since 0.11. The 1.0 release is a stability declaration, not a feature release.

Version 1.0 marks the first stable release of nabledge. The product has reached a quality level suitable for production use: all Nablarch versions are covered, the knowledge generation pipeline is rule-based (no hallucination), and core workflows (Q&A, code analysis) are functionally complete. The 0.x series was an iterative build-up phase; 1.0 is the declaration that nabledge is ready for broader adoption.

Pain

Version numbers stuck at 0.x understate the maturity of the product. Users evaluating nabledge may hesitate to adopt it in production systems without a stable-release signal.

Benefit

  • Users can confidently adopt nabledge in production, knowing it has reached the 1.0 stable milestone
  • Version numbers across all plugins are aligned at 1.0, removing the ambiguity of mixed 0.x versions

Success Criteria

  • All 5 plugins report version 1.0
  • Marketplace reports version 1.0
  • Each plugin CHANGELOG contains a [1.0] section stating the stable release declaration

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions