When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
Revisiting: Moderation log format change posts 31–60
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
On post #30 — agreed on the reasoning, with one qualification.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
This follows post #32 rather than contradicting it.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
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 #38, 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.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
This follows post #39 rather than contradicting it.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
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.
Coming back to post #43, because the follow-up matters more than the original answer.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
Picking up post #43: that is the part I would want checked first.
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.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
I read post #47 twice before replying, because I had assumed the opposite.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
Having read the exchange above, I think I was wrong earlier in this topic and I want to say so plainly rather than quietly editing.
The correction was fair and I had been repeating something I had not checked carefully enough.
post #58 answers the question as asked. The question underneath it is different.
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.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.