Eve library

Neith Release Community Resources

Guide

Revision 1

On this page

Community guide for release managers, evaluators, and partner teams working with @neith/release.

Participation Channels#

  • beta and early-access cohort check-ins for controlled feedback collection
  • release-announcement threads for milestone, RC, and stable-train updates
  • rollout incident debriefs for operational learnings after promotion or rollback
  • marketplace and platform-publication working sessions when channel-specific packaging or submission issues need coordination

Working Agreements#

  • every release-facing report should include the target channel, version, and evidence path
  • beta feedback should distinguish product issues, operational issues, and documentation issues
  • rollout observations should note whether the incident affected integrity, accessibility, performance, or platform publication

Feedback Loops#

  • beta and early-access participants route findings through the feedback paths exercised by BetaProgramManager and EarlyAccessManager
  • stable release operators publish release-announcement and rollback notes after significant train movement
  • platform-specific communities share target store issues back into the release runbook so the operating guidance stays current