Branching Policy - Revision history

Rpurdie at 10:20, 7 November 2012

2012-11-07T10:20:35Z

← Older revision		Revision as of 10:20, 7 November 2012
Line 1:		Line 1:
	~~Branches are going~~ to ~~fall roughly into three categories:~~		OE-Core has six month development and release cycles, roughly being April and October each year. As each release is made, the release is given a name and its expected that other layers/repositories that would with the release use the same branch name to denote compatibility.

	* Core branches (main dev branch, ~~documentation)~~		With the use of the git source control system, users are free and actively encouraged to create clones of the repositories to develop and submit changes against and they are also welcome to share branches in the contrib repositories as appropriate.
	* Topic branches (stable branch, openmoko branch, etc. - anything with an entity behind it and also ~~specific development targets if long running e.g. packaged-staging)~~
	* User branches (personal branches where users can share ~~hacks, request pulls into other~~ branches~~, request testing of new features etc~~.)

	~~Any~~ OE ~~developer~~ is free to request a personal user repository. User branches should clearly be identified as such and we'd caution about having large groups of users depending on them. Effort should be made by everyone concerned to get useful changes into the ~~Core or Topic branches.~~		For OE-Core, a maintainer is generally appointed for the release branch at release time and this is recommended for other layers too.

	~~Core~~ and ~~Topic branches should only be created after discussion and consensus.~~

	~~Mirrors should mirror the Core and Topic branches but the user branches should not be mirrored to encourage use of the core/topic branches~~.

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

Laibsch: Protected "Branching Policy" [edit=sysop:move=sysop]

2008-07-28T00:06:33Z

Protected "Branching Policy" [edit=sysop:move=sysop]

← Older revision	Revision as of 00:06, 28 July 2008
(No difference)

Laibsch at 00:06, 28 July 2008

2008-07-28T00:06:25Z

← Older revision		Revision as of 00:06, 28 July 2008
Line 10:		Line 10:

	Mirrors should mirror the Core and Topic branches but the user branches should not be mirrored to encourage use of the core/topic branches.		Mirrors should mirror the Core and Topic branches but the user branches should not be mirrored to encourage use of the core/topic branches.

			[[Category:Policy]]

Laibsch: New page: Branches are going to fall roughly into three categories: * Core branches (main dev branch, documentation) * Topic branches (stable branch, openmoko branch, etc. - anything with an entity...

2008-07-28T00:06:00Z

New page: Branches are going to fall roughly into three categories: * Core branches (main dev branch, documentation) * Topic branches (stable branch, openmoko branch, etc. - anything with an entity...

New page

Branches are going to fall roughly into three categories:

* Core branches (main dev branch, documentation)
* Topic branches (stable branch, openmoko branch, etc. - anything with an entity behind it and also specific development targets if long running e.g. packaged-staging)
* User branches (personal branches where users can share hacks, request pulls into other branches, request testing of new features etc.)

Any OE developer is free to request a personal user repository. User branches should clearly be identified as such and we'd caution about having large groups of users depending on them. Effort should be made by everyone concerned to get useful changes into the Core or Topic branches.

Core and Topic branches should only be created after discussion and consensus.

Mirrors should mirror the Core and Topic branches but the user branches should not be mirrored to encourage use of the core/topic branches.