168:
32:
95:
133:. Restoring the stable version is not required or encouraged by any policy or guideline, and administrators can fully protect articles mid-dispute, even if the protected version contains controversial edits. However, doing so can upset editors who did not get their preferred version protected, and they may complain that the admin has protected "
137:". Reverting to the stable version returns the article to neutral ground, and thus may help de-escalate a situation better than protecting one party's preferred version would. Administrators should consider what the best course of action is on a case-by-case basis, and neither option constitutes an admin's
150:
It is important to note that outside of the limited administrative context, a "stable version" is an informal concept that carries no weight whatsoever, and it should never be invoked as an argument in a content dispute. Maintaining a stable version is, by itself, not a valid reason to revert or
141:
in a dispute or an endorsement of the protected version of an article in any way. If an administrator protects an article without restoring the stable version, editors can still request that the stable version be restored by any administrator.
189:" was used to refer to a wide variety of proposals to implement a formal system to identify and maintain good-quality versions of articles—keeping them "stable" from any potential unwanted changes. Such proposals included
163:, rather than preserving the stable version, and the decision to temporarily preserve the stable version for the purposes of deescalating a dispute may only be made by an uninvolved administrator.
103:
Uninvolved administrators are authorized under policy to revert to and protect an older version of an article, as a means of resolving disputes and halting disruption.
151:
dispute edits, and should never be used as a justification to edit war. Stable versions are not superior or preferred to disputed edits in any way,
231:
was permanently implemented in
December 2012 and remains in effect to this day. The term "stable version" is no longer used in this context.
290:
40:
275:
17:
198:
155:
is encouraged as a matter of policy, and obstructing good faith edits for the sake of preserving "stable" content is a form of
270:
122:
285:
190:
206:
52:
138:
280:
130:
51:
This page provides additional information about concepts in the page(s) it supplements. This page is not one of
210:
194:
56:
225:. After many years of debate and controversy over "flagged revs", the variation of these proposals known as
245:
114:
218:
202:
44:
214:
227:
126:
250:
240:
134:
118:
74:
8:
66:
255:
173:
145:
152:
264:
113:
is the most recent revision of an article that was not affected by an active
222:
160:
156:
180:
172:
Editors who persistently attempt to enforce a stable version may be
159:. Editors involved in content disputes or edit wars should focus on
167:
125:
it (in response to such a content dispute or edit war) is a common
234:
121:. Restoring an article to the stable version when
262:
87:Explanatory essay about the Protection policy
14:
263:
89:
26:
129:practice that is authorized by the
24:
57:thoroughly vetted by the community
53:Knowledge's policies or guidelines
25:
302:
153:boldly making changes to articles
276:Knowledge essays about adminship
166:
93:
30:
291:Knowledge Administrators' guide
13:
1:
199:Stabilizing featured articles
271:Knowledge supplemental pages
246:Knowledge:Dispute resolution
7:
10:
307:
228:pending changes protection
185:Historically, the phrase "
64:
286:Knowledge page protection
18:Knowledge:Stable versions
101:This page in a nutshell:
251:Knowledge:FIXTHEPROBLEM
281:Knowledge edit warring
241:Knowledge:Edit warring
161:resolving the dispute
174:blocked from editing
195:Stable versions now
146:Inappropriate usage
55:as it has not been
207:Article validation
157:disruptive editing
256:Knowledge:Be bold
219:Flagged revisions
211:Reviewed versions
203:Baseline revision
135:the wrong version
131:Protection policy
107:
106:
85:
84:
45:Protection policy
41:explanatory essay
16:(Redirected from
298:
215:Community assent
181:Historical usage
176:without warning.
170:
123:fully protecting
97:
96:
90:
77:
34:
33:
27:
21:
306:
305:
301:
300:
299:
297:
296:
295:
261:
260:
237:
223:Pending changes
191:Stable versions
183:
148:
115:content dispute
94:
88:
81:
80:
73:
69:
61:
60:
31:
23:
22:
15:
12:
11:
5:
304:
294:
293:
288:
283:
278:
273:
259:
258:
253:
248:
243:
236:
233:
187:stable version
182:
179:
147:
144:
127:administrative
111:stable version
105:
104:
98:
86:
83:
82:
79:
78:
70:
65:
62:
50:
49:
37:
35:
9:
6:
4:
3:
2:
303:
292:
289:
287:
284:
282:
279:
277:
274:
272:
269:
268:
266:
257:
254:
252:
249:
247:
244:
242:
239:
238:
232:
230:
229:
224:
220:
216:
212:
208:
204:
200:
196:
192:
188:
178:
177:
175:
169:
164:
162:
158:
154:
143:
140:
136:
132:
128:
124:
120:
116:
112:
102:
99:
92:
91:
76:
72:
71:
68:
63:
58:
54:
47:
46:
42:
36:
29:
28:
19:
226:
186:
184:
171:
165:
149:
110:
108:
100:
38:
139:involvement
39:This is an
265:Categories
43:about the
75:WP:STABLE
235:See also
119:edit war
67:Shortcut
221:, and
109:The
117:or
267::
217:,
213:,
209:,
205:,
201:,
197:,
193:,
48:.
59:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
