This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
post #60 answers the question as asked. The question underneath it is different.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
Feedback to announcements: if you have feedback on an announced change (not a question, but your position) post it in the Meta category rather than here.
post #64 is right about the mechanism and I think understates the practical bit.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Worth separating two things that post #62 runs together.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
On post #66 — agreed on the reasoning, with one qualification.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
This follows post #69 rather than contradicting it.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
On post #73 — agreed on the reasoning, with one qualification.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Picking up post #78: that is the part I would want checked first.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Coming back to post #80, because the follow-up matters more than the original answer.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
New subcategory: rationale and scope
On the subject in the title: New subcategory: rationale and scope Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and the trust-level page and I…
|
+126 | 138 | 13k | 9mo |
|
Revisiting: Moderation log format change
Revisiting: Moderation log format change Writing it up because I had to work it out twice and would rather nobody else did. Process question about how this site works. I have read the guidelines and the…
|
+66 | 71 | 9.1k | 19mo |
|
About the Announcements category
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with…
|
+3 | 7 | 8.7k | 4h |
|
[2026 update] New subcategory: rationale and scope
New subcategory: rationale and scope — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
+142 | 163 | 1.8k | 18mo |
|
A staff appointment, and what the role involves
On the subject in the title: A staff appointment, and what the role involves Working notes rather than a conclusion. Nominating something for promotion into the documentation commons. The topic in question…
|
2 | 1.8k | 4mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Pricing far outside the range, in either direction
Posting this under the heading it deserves: Pricing far outside the range, in either direction Everything below is what sits behind that. Structured report rather than an opinion, following the format the…
|
+3 | 7 | 27k | 7mo |
|
Coming back to: When a red flag was a misunderstanding, and the retraction
When a red flag was a misunderstanding, and the retraction I have a specific reason for asking rather than idle curiosity, and the context is below. A logistics question, since the answers here are usually…
|
+6 | 10 | 257 | 21h |
|
What to include when your question involves a laboratory result — a second dataset
What to include when your question involves a laboratory result — a second dataset I have a specific reason for asking rather than idle curiosity, and the context is below. Question in the title. Context…
|
2 | 7k | 23d | |
|
Follow-up: A supplier that answers analytical questions with restated claims
A supplier that answers analytical questions with restated claims — setting out what I have, and where I think it stops being reliable. A logistics question, since the answers here are usually better than…
|
+74 | 82 | 2.8k | 6mo |
|
A revision dispute resolved on the topic rather than in the history
A revision dispute resolved on the topic rather than in the history Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the documentation…
|
+11 | 15 | 40k | 16h |