VNext: Difference between revisions

Line 1:

'''vNext''' is the upcoming development hive of [[OpenXP]], intended for fundamental changes. Ideologically, it is principally derives abandoned <code>nova</code> branch, but with relatively new approach.

== Structure ==

Before 2025, vNext development was done exclusively on <code>vnext</code> branch, without reverse-integrations and subbranches. However, this approach declared continuous mess of source code which wasn't separated from code base.

To keep things sorted out, vNext branches started with <code>vx</code> prefix, and it's mainstream branch is <code>vx_core</code>. Another subbranches will available eventually, as the earliest available subbranch is <code>vx_core_architect</code>. Continually, after stabilizing all vNext development results it will be reverse integrated with <code>master</code> branch, and it's results will appear on public patch kits.

== Planned features ==

@@ Line 1: / Line 1: @@
 '''vNext''' is the upcoming development hive of [[OpenXP]], intended for fundamental changes. Ideologically, it is principally derives abandoned <code>nova</code> branch, but with relatively new approach.
+== Structure ==
+Before 2025, vNext development was done exclusively on <code>vnext</code> branch, without reverse-integrations and subbranches. However, this approach declared continuous mess of source code which wasn't separated from code base.
+To keep things sorted out, vNext branches started with <code>vx</code> prefix, and it's mainstream branch is <code>vx_core</code>. Another subbranches will available eventually, as the earliest available subbranch is <code>vx_core_architect</code>. Continually, after stabilizing all vNext development results it will be reverse integrated with <code>master</code> branch, and it's results will appear on public patch kits.
 == Planned features ==