Posting this under the heading it deserves: Scheduled maintenance and what will be unavailable Everything below is what sits behind that.
Scheduled maintenance: setting out the arithmetic in full, because I have had to do it twice and I would rather nobody else did.
Every step is shown. If the answer is wrong the error will be visible, which is the point of writing it out rather than posting the result.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
That is all I can say without guessing.
The rare case here is the one that costs somebody a week, though, and the common case costs everyone ten seconds. I think the trade is clearly correct.
If that is already documented somewhere, ignore me and link it.
Posting my Scheduled maintenance numbers with the method attached so they can be discounted properly. Uncontrolled, unblinded, and collected by someone who wanted a particular answer.
Adding a small correction to the Scheduled maintenance summary above rather than a disagreement with it. The substance holds; one of the figures is out by a factor that matters.
Scheduled maintenance is a good example of a question where the honest answer is boring and the interesting answers are unsupported. I would go with boring.
Post #9 is the version of this I will quote in future. One addition.
Worth saying publicly: stepping back cleanly and handing over is a service. Documents with an absent maintainer go wrong quietly, which is the worst way for them to go wrong.
On balance I think that is right, and I would not bet much on it.
Where the Scheduled maintenance reasoning breaks down for me is the step from the group result to the individual case. That step is almost never argued for.
Post #14 put the caveat in the right place and I want to underline it.
Distinguishing three things in the Scheduled maintenance discussion that keep getting used interchangeably: the observation, the proposed mechanism, and the recommendation that gets attached to both.
Building on post #14 rather than restating it.
An update on my earlier Scheduled maintenance post: the pattern held for another six weeks and then stopped, which I did not predict and cannot explain.
The rare case here is the one that costs somebody a week, though, and the common case costs everyone ten seconds. I think the trade is clearly correct.
Two people can read the same figure differently here and both be reasonable.
Useful. I had the fact and not the reason, which turns out to be the important half.
Scheduled maintenance notice. The site will be read-only for a short window; nothing will be lost and nothing needs doing at your end. If a post fails to submit during it, the draft survives.
Worth saying publicly: stepping back cleanly and handing over is a service. Documents with an absent maintainer go wrong quietly, which is the worst way for them to go wrong.
I would keep Scheduled maintenance and the decision it usually gets used for separate in this thread. They are related and they are not the same question, and merging them is why the last one went badly.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Moderation log format change
Posting this under the heading it deserves: Moderation log format change Everything below is what sits behind that. Moderation log format change keeps being re-asked here and I think that is because the…
|
+53 | 57 | 4.8k | 2mo |
|
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. Trust level 3 requirements, and specifically the version of it that the documentation does not…
|
+10 | 14 | 7k | 9mo |
|
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. Reading back through what has been written here about staff appointment, three…
|
2 | 1k | 22mo | |
|
Trust level 3 requirements: a clarification — does this still hold?
Asking directly, because I could not find a straight answer: Trust level 3 requirements: a clarification — does this still hold? Two things I would like separated before anyone answers on Trust level 3…
|
+77 | 90 | 57k | 9h |
|
[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. Proposing that New subcategory deserves a maintained page rather than a recurring topic, and drafting…
|
+136 | 163 | 1.8k | 18mo |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Whether an aggregate is worth publishing at all: a disputed topic
On the subject in the title: Whether an aggregate is worth publishing at all: a disputed topic Working notes rather than a conclusion. An honest uncertainty about whether an aggregate rather than a disguised…
|
+20 | 24 | 18k | 13mo |
|
Search filters: what is missing
Search filters: what is missing — setting out what I have, and where I think it stops being reliable. Search filters — I have the observation and I do not trust my interpretation of it, so I am posting the…
|
+72 | 84 | 15k | 3d |
|
Request declined, with reasoning
Request declined, with reasoning — setting out what I have, and where I think it stops being reliable. I would like to know what people here actually do about request declined, as distinct from what is…
|
+2 | 6 | 173 | 13mo |
|
I joined for one answer and stayed for a year — what changed my mind
Posting this under the heading it deserves: I joined for one answer and stayed for a year — what changed my mind Everything below is what sits behind that. Question in the title and the context underneath, in…
|
+95 | 114 | 17k | just now |
|
Why the timeline is on the right and not the left
Why the timeline is on the right and not the left — that is the question, and I have not found it answered plainly anywhere I have looked. Something about timeline does not reconcile and I would like a second…
|
+67 | 73 | 19k | 10mo |