Feather Framework
English

Appearance

Release plan

A usable alpha in Q1 2027.

Feather will call itself alpha when a server owner can install it, configure it, operate it, and upgrade it with a documented path—not simply when the individual resources run.

Target windowMarch 2027Public usable alpha
Scope before dates

The release moves when its required contracts are ready. Optional features do not hold alpha.

Integration over demos

A resource is ready when it works through supported contracts and survives restart and upgrade paths.

Documentation is release work

Setup, configuration, API references, ownership boundaries, and migration notes ship with the code.

Sep–Oct 2026
Foundation freeze

Stabilize the framework contracts

  • Freeze the Alpha contract surface for Core, Character, Inventory, Roles, Routing, World, and Toolkit.
  • Finish ACL and policy ownership between Core, Admin, Inventory, and future access resources.
  • Remove duplicate legacy surfaces from the primary documentation path.
  • Define supported dependency and resource start order.
Nov–Dec 2026
Alpha candidate

Prove installation and integration

  • Exercise clean installs through the official recipe on Windows and Linux.
  • Complete contract, persistence, restart, migration, and failure-path smoke tests.
  • Validate the server-owner configuration path without requiring code changes.
  • Publish complete API signatures, examples, and resource ownership guidance.
January 2027
Closed alpha

Run real servers on the candidate

  • Onboard a small group of server owners and resource developers.
  • Collect installation, operations, upgrade, performance, and integration failures.
  • Accept bug fixes and documentation corrections; defer new optional features.
February 2027
Stabilization

Resolve release blockers

  • Close critical data-loss, security, identity, permission, and lifecycle defects.
  • Confirm recovery procedures and safe migration behavior.
  • Lock the Alpha release notes and known limitations.
March 2027
Public alpha

Release a usable Alpha

  • Publish tagged, compatible resource releases and the matching recipe.
  • Publish server-owner setup, developer references, upgrade notes, and known limitations.
  • Open a defined support and issue-triage process for Alpha adopters.
Q2 2027+
After alpha

Measure the path to Beta

Beta timing will be based on Alpha adoption and defect trends. Future-release work such as nested containers, trading, selectable ledger themes, sorting, favorites, and optional hotbar cooldown hooks remains outside the Alpha gate.

Alpha release gate

What “usable” means

  • Clean installation succeeds from documented steps.
  • Core gameplay resources start and report healthy contracts.
  • Character identity and Inventory state persist safely.
  • Permissions fail closed and administrative actions are audited.
  • Restart and upgrade paths do not silently destroy player data.
  • Server owners can configure the supported experience without editing source code.