Release NixOS 22.11

  - made sure NixOS tests are [linked](https://nixos.org/manual/nixpkgs/unstable/#ssec-nixos-tests-linking) to the relevant packages

- [ ] Tested compilation of all packages that depend on this change using `nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"`. Note: all changes have to be committed, also see [nixpkgs-review usage](https://github.com/Mic92/nixpkgs-review#usage)

- [ ] Tested basic functionality of all binary files (usually in `./result/bin/`)

- [22.11 Release Notes (or backporting 22.05 Release notes)](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#generating-2211-release-notes)

- [23.05 Release Notes (or backporting 22.11 Release notes)](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#generating-2305-release-notes)

  - [ ] (Package updates) Added a release notes entry if the change is major or breaking

  - [ ] (Module updates) Added a release notes entry if the change is significant

  - [ ] (Module addition) Added a release notes entry if adding a new NixOS module

Follow these steps to backport a change into a release branch in compliance with the [commit policy](https://nixos.org/nixpkgs/manual/#submitting-changes-stable-release-branches).

You can add a label such as `backport release-22.05` to a PR, so that merging it will

You can add a label such as `backport release-22.11` to a PR, so that merging it will

automatically create a backport (via [a GitHub Action](.github/workflows/backport.yml)).

This also works for PR's that have already been merged, and might take a couple of minutes to trigger.

You can also create the backport manually:

1. Take note of the commits in which the change was introduced into `master` branch.

2. Check out the target _release branch_, e.g. `release-22.05`. Do not use a _channel branch_ like `nixos-22.05` or `nixpkgs-22.05-darwin`.

2. Check out the target _release branch_, e.g. `release-22.11`. Do not use a _channel branch_ like `nixos-22.11` or `nixpkgs-22.11-darwin`.

3. Create a branch for your change, e.g. `git checkout -b backport`.

4. When the reason to backport is not obvious from the original commit message, use `git cherry-pick -xe <original commit>` and add a reason. Otherwise use `git cherry-pick -x <original commit>`. That's fine for minor version updates that only include security and bug fixes, commits that fixes an otherwise broken package or similar. Please also ensure the commits exists on the master branch; in the case of squashed or rebased merges, the commit hash will change and the new commits can be found in the merge message at the bottom of the master pull request.

5. Push to GitHub and open a backport pull request. Make sure to select the release branch (e.g. `release-22.05`) as the target branch of the pull request, and link to the pull request in which the original change was comitted to `master`. The pull request title should be the commit title with the release version as prefix, e.g. `[22.05]`.

5. Push to GitHub and open a backport pull request. Make sure to select the release branch (e.g. `release-22.11`) as the target branch of the pull request, and link to the pull request in which the original change was comitted to `master`. The pull request title should be the commit title with the release version as prefix, e.g. `[22.11]`.

6. When the backport pull request is merged and you have the necessary privileges you can also replace the label `9.needs: port to stable` with `8.has: port to stable` on the original pull request. This way maintainers can keep track of missing backports easier.

## Criteria for Backporting changes

- Services which require a client to be up-to-date regardless. (E.g. `spotify`, `steam`, or `discord`)

- Security critical applications (E.g. `firefox`)

## Generating 22.11 Release Notes

## Generating 23.05 Release Notes

Documentation in nixpkgs is transitioning to a markdown-centric workflow. Release notes now require a translation step to convert from markdown to a compatible docbook document.

Steps for updating 22.11 Release notes:

Steps for updating 23.05 Release notes:

1. Edit `nixos/doc/manual/release-notes/rl-2211.section.md` with the desired changes

2. Run `./nixos/doc/manual/md-to-db.sh` to render `nixos/doc/manual/from_md/release-notes/rl-2211.section.xml`

3. Include changes to `rl-2211.section.md` and `rl-2211.section.xml` in the same commit.

1. Edit `nixos/doc/manual/release-notes/rl-2305.section.md` with the desired changes

2. Run `./nixos/doc/manual/md-to-db.sh` to render `nixos/doc/manual/from_md/release-notes/rl-2305.section.xml`

3. Include changes to `rl-2305.section.md` and `rl-2305.section.xml` in the same commit.

## Reviewing contributions

system, [Hydra](https://hydra.nixos.org/).

* [Continuous package builds for unstable/master](https://hydra.nixos.org/jobset/nixos/trunk-combined)

* [Continuous package builds for the NixOS 22.05 release](https://hydra.nixos.org/jobset/nixos/release-22.05)

* [Continuous package builds for the NixOS 22.11 release](https://hydra.nixos.org/jobset/nixos/release-22.11)

* [Tests for unstable/master](https://hydra.nixos.org/job/nixos/trunk-combined/tested#tabs-constituents)

* [Tests for the NixOS 22.05 release](https://hydra.nixos.org/job/nixos/release-22.05/tested#tabs-constituents)

* [Tests for the NixOS 22.11 release](https://hydra.nixos.org/job/nixos/release-22.11/tested#tabs-constituents)

Artifacts successfully built with Hydra are published to cache at

https://cache.nixos.org/. When successful build and test criteria are

    <listitem>

      <para>

        <emphasis>Stable channels</emphasis>, such as

        <link xlink:href="https://nixos.org/channels/nixos-22.05"><literal>nixos-22.05</literal></link>.

        <link xlink:href="https://nixos.org/channels/nixos-22.05"><literal>nixos-22.11</literal></link>.

        These only get conservative bug fixes and package upgrades. For

        instance, a channel update may cause the Linux kernel on your

        system to be upgraded from 4.19.34 to 4.19.38 (a minor bug fix),

    <listitem>

      <para>

        <emphasis>Small channels</emphasis>, such as

        <link xlink:href="https://nixos.org/channels/nixos-22.05-small"><literal>nixos-22.05-small</literal></link>

        <link xlink:href="https://nixos.org/channels/nixos-22.05-small"><literal>nixos-22.11-small</literal></link>

        or

        <link xlink:href="https://nixos.org/channels/nixos-unstable-small"><literal>nixos-unstable-small</literal></link>.

        These are identical to the stable and unstable channels

  <para>

    When you first install NixOS, you’re automatically subscribed to the

    NixOS channel that corresponds to your installation source. For

    instance, if you installed from a 22.05 ISO, you will be subscribed

    to the <literal>nixos-22.05</literal> channel. To see which NixOS

    instance, if you installed from a 22.11 ISO, you will be subscribed

    to the <literal>nixos-22.11</literal> channel. To see which NixOS

    channel you’re subscribed to, run the following as root:

  </para>

  <programlisting>

</programlisting>

  <para>

    (Be sure to include the <literal>nixos</literal> parameter at the

    end.) For instance, to use the NixOS 22.05 stable channel:

    end.) For instance, to use the NixOS 22.11 stable channel:

  </para>

  <programlisting>

# nix-channel --add https://nixos.org/channels/nixos-22.05 nixos

# nix-channel --add https://nixos.org/channels/nixos-22.11 nixos

</programlisting>

  <para>

    If you have a server, you may want to use the <quote>small</quote>

    channel instead:

  </para>

  <programlisting>

# nix-channel --add https://nixos.org/channels/nixos-22.05-small nixos

# nix-channel --add https://nixos.org/channels/nixos-22.11-small nixos

</programlisting>

  <para>

    And if you want to live on the bleeding edge:

      also specify a channel explicitly, e.g.

    </para>

    <programlisting language="bash">

system.autoUpgrade.channel = https://nixos.org/channels/nixos-22.05;

system.autoUpgrade.channel = https://nixos.org/channels/nixos-22.11;

</programlisting>

  </section>

</chapter>

<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-release-22.11">

  <title>Release 22.11 (“Raccoon”, 2022.11/??)</title>

  <title>Release 22.11 (“Raccoon”, 2022.11/30)</title>

  <para>

    The NixOS release team is happy to announce a new version of NixOS

    22.11. NixOS is both a Linux distribution, and a set of packages