Release Process
Merge dev to main and publish release.
Release Schedule
Releases: Monday, Wednesday, Friday at 9am PST
Prerequisites
Before release:
- All PRs merged to
devbranch - All features tested
- Documentation updated on GitHub (CHANGELOG, README, ROADMAP, API docs)
- No blockers or critical bugs
Release Steps
1. Version Bump
Update version in massgen/__init__.py:
__version__ = "0.1.9"
2. Final Testing
Test dev branch:
- Run full test suite
- Test key features
- Verify documentation accuracy
3. Merge dev to main
git checkout main
git merge dev/vX.X.X
git push origin main
4. Create Git Tag
git tag v0.1.9
git push origin v0.1.9
5. Create GitHub Release
On GitHub:
- Go to Releases
- Click “Draft a new release”
- Select tag (v0.1.9)
- Release title: “v0.1.9”
- Copy content from CHANGELOG.md
- Publish release
Release Notes Format
## What's New in v0.x.x
### Feature A: Description
### Feature B: Description
### Getting Started
- Include link to video demo or case study (if available)
- Provide example `.yaml` configuration files for quick start
- List relevant documentation guide
## What's Changed
- List all merged PRs with format: `type: description by @username in #PR`
- Include types: feat, fix, docs, refactor, test, chore
- Link to PR numbers for full details
- Credit all contributors with @ mentions
**Full Changelog:** v0.1.8...v0.1.9
After Release
- Release is live on GitHub
- Main branch updated
- Next step: See Announcements to share with community
- Start next development cycle
Who Does This
Maintainers perform releases.
Release schedule: Regular cadence (Mon/Wed/Fri) ensures predictable releases.
Tracking Releases
- GitHub Releases: github.com/massgen/MassGen/releases
- CHANGELOG.md: Detailed version history
- Git Tags: Version markers in repository
Next Step
After release, see Announcements for sharing with community.
Contact
Nick Crispino
- Discord: nickcrispino
Henry
- Discord: henry_weiqi