This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
This follows post #61 rather than contradicting it.
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.
On post #61 — agreed on the reasoning, with one qualification.
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.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
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.
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.
post #69 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.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
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 |
|
Trust level 3 requirements: a clarification
Trust level 3 requirements: a clarification — 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…
|
+10 | 14 | 7k | 9mo |
|
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 | |
|
Revisiting: A staff appointment, and what the role involves
Revisiting: A staff appointment, and what the role involves — setting out what I have, and where I think it stops being reliable. Process question about how this site works. I have read the guidelines and the…
|
2 | 1k | 22mo | |
|
[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 |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Request: export my own posts — one year on
Request: export my own posts — one year on — 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…
|
+66 | 70 | 14k | 4mo |
|
Second pass at: The storage lookup and where its data comes from
On the subject in the title: Second pass at: The storage lookup and where its data comes from Working notes rather than a conclusion. A documentation question rather than an analytical one. I have a…
|
+38 | 42 | 13k | 19d |
|
Trust level 3 requirements: a clarification
Trust level 3 requirements: a clarification — 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…
|
+10 | 14 | 7k | 9mo |
|
Why we ask for units every single time, with three examples of what goes wrong — what changed since
The question in the title: Why we ask for units every single time, with three examples of what goes wrong — what changed since I will give what I have already checked below so nobody repeats it. Question in…
|
+14 | 18 | 19k | 2mo |
|
A supplier that answers analytical questions with restated claims
On the subject in the title: A supplier that answers analytical questions with restated claims Working notes rather than a conclusion. A logistics question, since the answers here are usually better than…
|
+107 | 118 | 45k | 12mo |