You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write docs/release-process.md: how work flows from a contributor PR on dev to a release on main, who performs the merge, how versions are chosen, and the deploy steps per app (backend service, Next.js app, AI agent, Soroban contracts). Cross-link the operator runbook for post-deploy verification.
Acceptance criteria:
The dev → main promotion flow is documented, including that only the maintainer merges to main
Per-app deploy steps are documented, including migration ordering relative to backend rollout
Contract deploys are covered as a distinct, non-rollback-able path, cross-linking the contracts deployment guide
States the rollback story for each app honestly, including where one does not exist
@Adedayo-Data has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi Maintainers,I'm a software developer with extensive experience in CI/CD release engineering, deployment runbooks, and Web3/Soroban contract lifecycles. I will draft docs/release-process.md detailing the dev → main promotion model, maintainer merge gates, versioning standards, and per-app deployment flows (backend service, Next.js frontend, AI agent, and Soroban contracts). I'll clearly document database migration ordering, cross-link the operator runbook and contract guides, and provide honest rollback protocols—including the immutable nature of smart contract rollbacks. I can submit a clean PR within 24 hours of assignment.
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Please assign this issue to me.
I’d like to work on this issue because a clear release and deployment process is an important part of maintaining a reliable software project, especially when the system consists of multiple applications and infrastructure components.
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
nobodieair commentedon Aug 27, 2026
@nobodieair has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @nobodieair to this issue.
zainmatty22 commentedon Aug 27, 2026
@zainmatty22 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @zainmatty22 to this issue.
Adedayo-Data commentedon Sep 23, 2026
@Adedayo-Data has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adedayo-Data to this issue.
KodeSage commentedon Sep 28, 2026
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @KodeSage to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
github-actions commentedon Sep 29, 2026
Closed by #613, merged into
dev.drips-wave commentedon Sep 29, 2026
This issue has been completed by @KodeSage as part of the Stellar Wave Program's 9th Wave 🥳
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.