Branch: Difference between revisions

Line 2:

== 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:

* '''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.

** '''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 ===

@@ Line 2: / Line 2: @@
 == 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:
 * '''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.
 ** '''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 ===