docs: track pre-launch notices for removal at public launch #383
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#383
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Remove the pre-launch / not-public notices at the public launch, tracked here so none of them rely on a future code sweep to be found.
Notices to remove or relax at launch
CONTRIBUTING.md- "madtea is not public yet ... work only after the public launch"docs/contributing/releasing.md- the pre-release notice (releases-page and package-manager links not reachable until launch)docs/contributing/releasing.md- "At the public launch each satellite moves to a public home"docs/contributing/github-source-sync.md- the pre-launch notice (themadtea.lolmodule path is not live until the rename plus the first release)Why
A pre-launch marker with no tracking issue rots in place and ships. This issue is the deliberate tracker, so the launch checklist removes each notice on purpose rather than hoping a sweep catches it.
Related: #380 (the madtea.lol migration), #381 (the release retooling that must land before the first release).
Mis-framed. madtea is already public on Codeberg (codeberg.org/sixfold_space/madtea, released through v0.18.3) - this is a migration, not a pre-launch. The transitional notices are not launch-gated; they come out when the madtea.lol migration completes. Folding that cleanup into the migration epic #420, and the notices now reference #420 for removal on completion.