Release only when Frederic asks
This commit is contained in:
parent
95cb4eeb7c
commit
5422116f36
2 changed files with 15 additions and 16 deletions
|
|
@ -10,13 +10,13 @@ Bumping `version` in `package.json` on `main` is the release button. The
|
|||
that version's CHANGELOG section as notes, and dispatches `release.yml`, which deploys
|
||||
to GitHub Pages (https://seriesoftub.es).
|
||||
|
||||
## Not everything needs a release
|
||||
## Only release when Frederic says so
|
||||
|
||||
Release only when there is something worth shipping to players: a feature, a fix they
|
||||
will notice, or a decent batch of smaller changes. Docs, skills, CI, issue templates,
|
||||
tests and refactors never need a release on their own; just push them. Small
|
||||
player-facing tweaks can sit under `## [Unreleased]` until a real release comes along.
|
||||
Don't plan a release just because the hour is up, and when unsure, ask the user.
|
||||
Never bump the version on your own. Finished work is committed and pushed with its
|
||||
bullets under `## [Unreleased]`, and you say it is ready to ship. A release happens only
|
||||
when Frederic explicitly asks for one ("release", "ship it"), and then it includes
|
||||
everything under `## [Unreleased]`. Docs, skills, CI, issue templates, tests and
|
||||
refactors are just pushed and never need a release.
|
||||
|
||||
## At most one release per hour
|
||||
|
||||
|
|
@ -27,13 +27,13 @@ most one release an hour. Before bumping, check when the last one went out:
|
|||
gh api repos/fjaeckel/seriesoftubes/releases/latest --jq '.tag_name+" "+.published_at'
|
||||
```
|
||||
|
||||
- **Less than 60 minutes ago:** don't bump. Commit and push the work with its bullets
|
||||
under `## [Unreleased]`; it goes out with the next release. Tell the user when the
|
||||
next release slot opens.
|
||||
- **Less than 60 minutes ago:** even when asked, say so and suggest waiting until the hour
|
||||
is up; release only if Frederic still wants it now.
|
||||
- **60 minutes or more:** release everything under `## [Unreleased]` together, as one
|
||||
version.
|
||||
- **Only exception:** the live game is broken for players (it won't start, saves are
|
||||
lost, a phone can't get past a screen). Then hotfix right away as a patch release.
|
||||
- **Live game broken for players** (it won't start, saves are lost, a phone can't get
|
||||
past a screen): tell Frederic right away and propose a hotfix release; still wait for
|
||||
his go.
|
||||
|
||||
## Pick the version
|
||||
|
||||
|
|
|
|||
|
|
@ -26,11 +26,10 @@ To play during development, open `site/index.html` directly or run `npm run serv
|
|||
- **Git:** work on `main`, no branches. Commits are authored and committed as
|
||||
`Frederic Jung <frederic@jc-ix.net>`. Never add `Co-Authored-By`, `Claude-Session`
|
||||
or any other attribution trailers.
|
||||
- **Releases** happen by bumping `version` in `package.json` on `main` (see the
|
||||
`release` skill). Small fixes or tweaks get a patch release (`x.y.Z`); new features a
|
||||
minor release. **Not everything needs a release**: docs, skills, CI, tests and refactors are just pushed, and small player-facing tweaks wait under `## [Unreleased]` for a real release. **At most one release per hour**: until the hour is up, push work with
|
||||
its CHANGELOG bullets under `## [Unreleased]` and batch it into the next release. Only a
|
||||
broken live game justifies an immediate hotfix.
|
||||
- **Releases only when Frederic says so.** Never bump the version on your own: push finished
|
||||
work with its CHANGELOG bullets under `## [Unreleased]` and say it is ready. When he asks
|
||||
for a release, follow the `release` skill: small fixes get a patch (`x.y.Z`), features a
|
||||
minor, at most one release per hour. Docs, skills, CI, tests and refactors never need one.
|
||||
- **Release notes in the app are short**: only the first sentence of each CHANGELOG bullet
|
||||
(and at most five bullets) shows in "What's new", with a link to the full GitHub
|
||||
release. Write that first sentence so it stands on its own.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue