Show what changed after an update #683
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung#683
Loading…
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?
Description
After an update, the people who run the club in Mila (board, treasurer, admins) only learn what changed if someone reads the release notes on the code forge. Those are written for the people who operate the instance. A change that affects the club's daily work goes unnoticed: from 1.6.0 on, admission and rejection mails are sent by default, also in existing clubs (#668), and the board should check the texts before the next approval.
Proposal
Content
priv/with 0–5 entries. Each entry has: a title, one sentence, the area it concerns (members, fees, join requests, settings …), whether it needs an action, and an optional link to the place in Mila or to the docs. Texts go through gettext. The data file is read at compile time; no database table for content.Who sees it
When and how
Mv.BuildInfoprovides the running version). Development builds between releases show nothing new.Out of scope
Club-specific announcements by the board, images, read statistics, a per-club switch (later, communication milestone).
Decisions for the design
Acceptance criteria
Dependencies