Ubuntu Kernel Next workflow
===========================

UKN is a periodical read-only snapshot of Ubuntu linux-unstable, thus no patches
will ever be directly merged in - they will reach linux-unstable first, and
then percolate down to UKN in the subsequent sync phase.

.. graphviz:: workflow.dot

- **Sync**: periodically, after linux-unstable has been rebased on a new major
  release and it reached a level of maturity, UKN will take a snapshot of it.

- **Fork + devel**: consumer of **UKN vX** forks the tree on Gitea, and start
  working on it (e.g. patchset A).

- **Pull req. A**: once patchset A is ready, a pull request will be sent against **UKN vX**.

- **Merge pull req. A**: assuming patchset A is sound, follows Ubuntu `patches guideline`_ and `acceptance criteria`_, the Ubuntu kernel team will step in, take patchset A and apply it to **linux-unstable vX+1**.

- **Sync**: at the susequent sync step between **linux-unstable** and **UKN**, patchset A will finally show up in **UKN vX+1**.

Wash, rinse and repeat.

.. _patches guideline: ubuntu_code_patches.html

.. _acceptance criteria: ubuntu_acceptance_criteria.html