case 4690 - release procedure: one documented sequence from code-complete to announcement
devdocs/build/RELEASE-PROCEDURE.md replaces John's notes from several info cases: release order with subscription droplets upgraded before the announcement, git tagging, scp uploads, the download-back check, upgrade commands with curl -f, the one-time 8.3.0 droplet steps (harden-830.sh), the weekly OS update and the full version bump list. BUILD.md's partial version table now points to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -97,5 +97,6 @@ dotnet publish server\AyaNova\AyaNova.csproj -c Release -r linux-x64 --no-self-c
|
||||
| `devdocs/modernization/PROJECT-OVERVIEW.md` | Products, deployment targets, business context |
|
||||
| `devdocs/modernization/CODEBASE-REFERENCE.md` | Stack, structure, configuration, API conventions |
|
||||
| `devdocs/modernization/TESTING.md` | Test suites and their state |
|
||||
| `devdocs/build/BUILD.md` | Release build, packaging, version numbers |
|
||||
| `devdocs/build/BUILD.md` | Release build, packaging |
|
||||
| `devdocs/build/RELEASE-PROCEDURE.md` | Release steps from code-complete to announcement, tagging, subscription droplet upgrades and weekly updates, version bump |
|
||||
| `devdocs/build/DEV-VM-SETUP.md` | Deprecated build VM plan; its tool list still serves for setting up a build machine. Releases are built on the workstation |
|
||||
|
||||
Reference in New Issue
Block a user