Branch - Revision history

Ashific at 06:18, 28 July 2025

2025-07-28T06:18:14Z

← Older revision		Revision as of 06:18, 28 July 2025
Line 8:		Line 8:
	Plenty of others are included in following structure:		Plenty of others are included in following structure:

	* '''General~~'''~~ branches are main development branches, which include new stuff, often not synchronized with <code>master</code>, but fetching stabilized changes from other branches below.		=== General ===
	* '''Feature branch leverage''' branches (<code>fbl</code>), which are intended for ~~development of a big program or change, which will be integrated into the system consequently. For example: implementation of a package manager or rejuvenated Feedback Tool.~~		General branches are main development branches, which include new stuff, often not synchronized with <code>master</code>, but fetching stabilized changes from other branches below. They are intended for keeping most groundbreaking changes, which have been tested properly and guarantee stability of their work. Future patch kits and releases of OpenXP are derived from these branches.
	* [[VNext\|'''vNext''']] '''branch family''' includes platform and groundbreaking ~~code~~ changes, ~~intended for fundamentally new features~~ and ~~improvements, e.g. ` fulfilled AMD64 port~~ of ~~source code, implementation of OpenKernel and more~~.
	* '''Highly experimental''' branches contain very sensitive and unstable improvements, with their consequences and ~~developing behavior may seem... funny. Yeah, lots~~ of ~~informal (and maybe even rude) expressions, crappy working programs, etc.~~
	** '''Fundamental''' branches (<code>fun</code>) are for crucial changes inside build environment and core facilities, leveraging platform changes and behavior. It may break compatibility with older applications, and it is in active development, meaning that core improvements will appear.
	** '''Funny''' branches (<code>lol</code> and similar) are ~~for lots of informal descriptions, preliminary naming, graphics, early programs and more. Even internal functionality may differ~~ from ~~that, but don't worry -~~ these branches ~~aren't for retail release, and they mostly exist in private circles of developers~~.

	=== Legacy mechanism ===		=== Feature branch leverage ===
	Before [[development reset]], OpenXP used labs system. <code>master</code> was still in existence, therefore most of branches didn't have any prefixes for their meaning, and used direct naming convention instead: <code>canary</code> was the ~~prerelease~~ improvements branch, and <code>fundamental</code> included all compiler enhancements.		Feature branch leverage branches (<code>fbl</code>) are intermediate branches, which are intended for long term development, which will be integrated into the system consequently. e.g. ` implementation of a package manager or rejuvenated Feedback Tool. These branches are serving as a foundation to merge into General branches, and they are not guarantee for stability.

			[[vNext]] branches are also belong to Feature branch leverage and they contain fundamental changes in kernel, back ports of multiple features and more. Apart of this, vNext branches are logical continuation of new, future releases and are first candidates to be merged into General ones usually.

			=== Funny ===
			This kind of branches contain very sensitive and unstable improvements, with their consequences and developing behavior may seem... funny. Yeah, lots of informal (and maybe even rude) expressions, crappy working programs and etc are here, and if you run build from these branches, never except anything, not talking about even stability.
			* '''Fundamental''' branches (<code>fun</code>) are for crucial changes inside build environment and core facilities, leveraging platform changes and behavior. It may break compatibility with older applications, and it is in active development, meaning that core improvements will appear.
			* '''Funny''' branches (<code>lol</code> and similar) are for lots of informal descriptions, preliminary naming, graphics, early programs and more. Even internal functionality may differ from that, but don't worry - these branches aren't for retail release, and they mostly exist in private circles of developers.

			== Legacy mechanism ==
			Before [[development reset]], OpenXP used labs system. <code>master</code> was still in existence, therefore most of branches didn't have any prefixes for their meaning, and used direct naming convention instead: <code>canary</code> was the pre-release improvements branch, and <code>fundamental</code> included all compiler enhancements. However, this branching mechanism was abandoned due to it's unusable and messy behavior.

	[[Category:Development]]		[[Category:Development]]

Ashific at 16:59, 3 June 2025

2025-06-03T16:59:09Z

← Older revision		Revision as of 16:59, 3 June 2025
Line 2:		Line 2:

	== Structure ==		== Structure ==
	The topmost branch is <code>master</code>, which contains the latest changes and edits, which are mostly stable. ~~<code>master</code> is the root branch, as others~~ are deriving directly from it, containing up-to-date changes in themselves too.		The topmost branch is <code>master</code>, which contains the latest changes and edits, which are mostly stable. Other branches are deriving directly from it, containing up-to-date changes in themselves too.

	Compilations derived from branches can be '''online''' and '''offline''', with the main difference being the inclusion of developer's username after branch name in '''online''' compiles (for example <code>master('''ash''')</code>), ~~which means an internal compiler for unit tests~~ and ~~build quality~~ of ~~life tracking~~.		Compilations derived from branches can be '''online''' and '''offline''', with the main difference being the inclusion of developer's username after branch name in '''online''' compiles (for example <code>master('''ash''')</code>), indicating of inclusion of in-development and partially private pieces of code.

	Plenty of others are included in following structure:		Plenty of others are included in following structure:

	* '''General''' branches are main development branches, which include new stuff, often not synchronized with <code>master</code>, but fetching stabilized changes from other branches below.		* '''General''' branches are main development branches, which include new stuff, often not synchronized with <code>master</code>, but fetching stabilized changes from other branches below.
	* '''Feature branch leverage''' branches (<code>fbl</code>), which are intended for development of a big program or change, which will be integrated into the system consequently. For example: implementation of a package manager or rejuvenated Feedback ~~tool~~.		* '''Feature branch leverage''' branches (<code>fbl</code>), which are intended for development of a big program or change, which will be integrated into the system consequently. For example: implementation of a package manager or rejuvenated Feedback Tool.
	* '''~~Nova~~''' ~~branches (<~~code~~>nova</code>) are~~ for ~~early~~ and ~~in-development programs~~, ~~which contain internal rewrites and newer implementations~~ of ~~crucial components~~, ~~which serve as a replacement, or an enhancement to existing programs. For example: new compilers~~.		* [[VNext\|'''vNext''']] '''branch family''' includes platform and groundbreaking code changes, intended for fundamentally new features and improvements, e.g. ` fulfilled AMD64 port of source code, implementation of OpenKernel and more.
	* '''Highly experimental''' branches contain very sensitive and unstable improvements, with their consequences and developing behavior may seem... funny. Yeah, lots of informal (and maybe even rude) expressions, crappy working programs, etc.		* '''Highly experimental''' branches contain very sensitive and unstable improvements, with their consequences and developing behavior may seem... funny. Yeah, lots of informal (and maybe even rude) expressions, crappy working programs, etc.
	** '''Fundamental''' branches (<code>fun</code>) are for crucial changes inside build environment and core facilities, leveraging platform changes and behavior. It may break compatibility with older applications, and it is in active development, meaning that core improvements will appear.		** '''Fundamental''' branches (<code>fun</code>) are for crucial changes inside build environment and core facilities, leveraging platform changes and behavior. It may break compatibility with older applications, and it is in active development, meaning that core improvements will appear.
	** '''Funny''' branches (<code>lol</code> and similar) are for ~~extreme edits, but with~~ lots of informal descriptions, preliminary naming and ~~graphics~~. Even internal functionality may differ from that, but don't worry - these branches aren't for retail release, and they mostly exist in private circles of developers.		** '''Funny''' branches (<code>lol</code> and similar) are for lots of informal descriptions, preliminary naming, graphics, early programs and more. Even internal functionality may differ from that, but don't worry - these branches aren't for retail release, and they mostly exist in private circles of developers.

	=== Legacy mechanism ===		=== Legacy mechanism ===

Ashific: Created page with "'''Branch''' is a development lab, initialized by OpenXP developers for making development more organized and consistent. Branches have different development structure and meaning, therefore their hierarchy is simpler and easier in plan of organization. == Structure == The topmost branch is `master`, which contains the latest changes and edits, which are mostly stable. `master` is the root branch, as others are deriving directly from it, containing..."

2025-06-02T16:47:29Z

Created page with "'''Branch''' is a development lab, initialized by OpenXP developers for making development more organized and consistent. Branches have different development structure and meaning, therefore their hierarchy is simpler and easier in plan of organization. == Structure == The topmost branch is <code>master</code>, which contains the latest changes and edits, which are mostly stable. <code>master</code> is the root branch, as others are deriving directly from it, containing..."

New page

'''Branch''' is a development lab, initialized by OpenXP developers for making development more organized and consistent. Branches have different development structure and meaning, therefore their hierarchy is simpler and easier in plan of organization.

== Structure ==
The topmost branch is <code>master</code>, which contains the latest changes and edits, which are mostly stable. <code>master</code> is the root branch, as others are deriving directly from it, containing up-to-date changes in themselves too.

Compilations derived from branches can be '''online''' and '''offline''', with the main difference being the inclusion of developer's username after branch name in '''online''' compiles (for example <code>master('''ash''')</code>), which means an internal compiler for unit tests and build quality of life tracking.

Plenty of others are included in following structure:

* '''General''' branches are main development branches, which include new stuff, often not synchronized with <code>master</code>, but fetching stabilized changes from other branches below.
* '''Feature branch leverage''' branches (<code>fbl</code>), which are intended for development of a big program or change, which will be integrated into the system consequently. For example: implementation of a package manager or rejuvenated Feedback tool.
* '''Nova''' branches (<code>nova</code>) are for early and in-development programs, which contain internal rewrites and newer implementations of crucial components, which serve as a replacement, or an enhancement to existing programs. For example: new compilers.
* '''Highly experimental''' branches contain very sensitive and unstable improvements, with their consequences and developing behavior may seem... funny. Yeah, lots of informal (and maybe even rude) expressions, crappy working programs, etc.
** '''Fundamental''' branches (<code>fun</code>) are for crucial changes inside build environment and core facilities, leveraging platform changes and behavior. It may break compatibility with older applications, and it is in active development, meaning that core improvements will appear.
** '''Funny''' branches (<code>lol</code> and similar) are for extreme edits, but with lots of informal descriptions, preliminary naming and graphics. Even internal functionality may differ from that, but don't worry - these branches aren't for retail release, and they mostly exist in private circles of developers.

=== Legacy mechanism ===
Before [[development reset]], OpenXP used labs system. <code>master</code> was still in existence, therefore most of branches didn't have any prefixes for their meaning, and used direct naming convention instead: <code>canary</code> was the prerelease improvements branch, and <code>fundamental</code> included all compiler enhancements.

[[Category:Development]]