Merge pull request 'docs(safety): the demo gets report, block and hide from the module release' (#404) from docs/user-safety-demo-release into main
Reviewed-on: #404
This commit is contained in:
@@ -298,8 +298,11 @@ Play declarations gain "user-generated content: collected". M21 says so.
|
||||
`rust.chat.unhide`.
|
||||
|
||||
**What the walk found about the demo itself.** The org lead's answer (2026-10-30) was **none of
|
||||
them**: the demo's chat audience, its seed and play-review's role stay as they are, and no
|
||||
Module-Rust release is cut for the demo.
|
||||
them**: the demo's chat audience, its seed and play-review's role stay as they are. That answer
|
||||
was about the demo's data. It was not about holding the features back. **Corrected the same
|
||||
day:** report, block and hide stay in the app, and the demo gets them in the ordinary way, from
|
||||
the module release. Module-Rust#73 cuts `edge` over to `main` as v0.7.0, and the demo's next wipe
|
||||
installs it (DM12). Nothing is seeded for it.
|
||||
|
||||
- **W1. The demo shows no chat to members.** Its `demo` server inherits the fleet's presence
|
||||
default, `staff`, so demo-player and a signed-out visitor see no feed at all. Only demo-admin,
|
||||
@@ -311,6 +314,8 @@ Play declarations gain "user-generated content: collected". M21 says so.
|
||||
the menu and see staff-hidden lines, and the block refusal and *Not applied* (S8) do not apply
|
||||
to them. They can still report, hide and block.
|
||||
- **W4. The demo runs Module-Rust v0.6.3**, the newest release, which has neither this feature
|
||||
nor account deletion's unlink (#70, #72 are on `edge`). The edge → `main` cutover was held so
|
||||
the demo is not changed by its next wipe.
|
||||
6. Then `android/PLAN.md` M8's cutover (S5).
|
||||
nor account deletion's unlink (#70, #72 are on `edge`). Fixed by the cutover above,
|
||||
Module-Rust#73 (v0.7.0).
|
||||
6. Then `android/PLAN.md` M8's cutover (S5): Android-app#65 (v0.7.0), with Module-Rust#73 as its
|
||||
server half. Before it merges, the org lead enrolls the release keystore as Play's app-signing
|
||||
key.
|
||||
|
||||
Reference in New Issue
Block a user