Revert Policy - Revision history

Rpurdie at 10:13, 7 November 2012

2012-11-07T10:13:16Z

← Older revision		Revision as of 10:13, 7 November 2012
Line 1:		Line 1:
	~~{{Outdated}}~~		Reverting someone elses work can be a great source of friction in OE. As such, these need to be handled carefully, preferable on technical grounds rather than personal ones. Some cases are clear, e.g. if the orignal patch author requests a revert then this should generally be accepted.

	~~Reverting someone elses work~~ is ~~by far~~ the ~~greatest source of friction~~		Now that OE uses layers, the situation is relatively clear since each layer has clear and documented maintainership and it is up to the layer maintainership to make decisions on whether code should be reverted.
	~~in OE. As such, these need~~ to be ~~handled carefully, preferable on~~
	~~technical grounds rather than personal ones~~.

	~~Reverts may only be carried out with either~~		In cases where there is any doubt, the OE TSC has final decision and authority.
	~~# Acks from two~~ TSC ~~members not associated with original change.~~
	~~# An Ack from the original patch author.~~

	~~This means you may revert your own mistakes~~.

	[[Category:Policy]]		[[Category:Policy]]
	[[Category:Quality Assurance]]		[[Category:Quality Assurance]]

PaulEggleton at 17:54, 3 November 2012

2012-11-03T17:54:50Z

← Older revision		Revision as of 17:54, 3 November 2012
Line 1:		Line 1:
			{{Outdated}}

	Reverting someone elses work is by far the greatest source of friction		Reverting someone elses work is by far the greatest source of friction
	in OE. As such, these need to be handled carefully, preferable on		in OE. As such, these need to be handled carefully, preferable on

Eric: Undo revision 3317 by Yjytalamago (Talk)

2010-11-24T07:43:50Z

Undo revision 3317 by Yjytalamago (Talk)

← Older revision	Revision as of 07:43, 24 November 2010
(No difference)

Sledz at 15:32, 30 August 2010

2010-08-30T15:32:00Z

← Older revision		Revision as of 15:32, 30 August 2010
Line 10:		Line 10:

	[[Category:Policy]]		[[Category:Policy]]
			[[Category:Quality Assurance]]

188.220.34.37 at 20:40, 24 August 2010

2010-08-24T20:40:26Z

← Older revision		Revision as of 20:40, 24 August 2010
Line 1:		Line 1:
	~~A revert~~ is ~~a special type~~ of ~~commit which undos another commit~~. ~~This is our policy for reverts:~~		Reverting someone elses work is by far the greatest source of friction
			in OE. As such, these need to be handled carefully, preferable on
			technical grounds rather than personal ones.

	# ~~Reverting your own commit is never a problem. This can be necessary to fix an important bug introduced by your commit or something you accidently committed~~.		Reverts may only be carried out with either
	# ~~Reverting a commit of another user is a problem~~. ~~If you wish to do so, please post a request for comments to the mailing list and wait until~~ you ~~either get the ACK of the committer or two ACKs non-committer ACKs. Do _not_~~ revert ~~before getting any of those ACKs~~.		# Acks from two TSC members not associated with original change.
			# An Ack from the original patch author.

			This means you may revert your own mistakes.

	[[Category:Policy]]		[[Category:Policy]]

Mickey: add revert policy

2010-08-24T17:47:50Z

add revert policy

New page

A revert is a special type of commit which undos another commit. This is our policy for reverts:

# Reverting your own commit is never a problem. This can be necessary to fix an important bug introduced by your commit or something you accidently committed.
# Reverting a commit of another user is a problem. If you wish to do so, please post a request for comments to the mailing list and wait until you either get the ACK of the committer or two ACKs non-committer ACKs. Do _not_ revert before getting any of those ACKs.

[[Category:Policy]]