diff --git a/content/architecture/apis-and-services.md b/content/architecture/apis-and-services.md
index 15bc6691b7a6a32813a9bb4dc4170469c8725163..2ea0b1fbfd343f3d05a324e67d90241bfb691e80 100644
--- a/content/architecture/apis-and-services.md
+++ b/content/architecture/apis-and-services.md
@@ -199,23 +199,23 @@ Full package list in TSV format, categorized under different repository componen
type which implements MxItemfactory. Model to give the MVC approach to the
app inspired by ClutterModel.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | UI utility library | [libthornbury API](https://docs.apertis.org/libthornbury/libthornbury/) | <https://gitlab.apertis.org/hmi/libthornbury> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | UI utility library | <https://gitlab.apertis.org/hmi/libthornbury> |
- **liblightwood**: libLightwood is a widget library. It has all the basic
widgets like buttons, lists, rollers, webviews, widgets, multilines and
textboxes, and can be extended to add functionality to these base widgets.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Widget library | [liblightwood API](https://docs.apertis.org/liblightwood/lightwood/) | <https://gitlab.apertis.org/hmi/liblightwood> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Widget library | <https://gitlab.apertis.org/hmi/liblightwood> |
- **Mildenhall**: Provides the reference UI widgets, used by graphical applications.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | User interface widget library | [Mildenhall API](https://docs.apertis.org/mildenhall/MILDENHALL-widgets/) | <https://gitlab.apertis.org/hmi/mildenhall> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | User interface widget library | <https://gitlab.apertis.org/hmi/mildenhall> |
## Enabling Components
@@ -261,71 +261,71 @@ Full package list in TSV format, categorized under different repository componen
handling and management), data exchange service (to facilitate
inter-application data exchange) being 2 examples.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Application management and process control service | [Canterbury API](https://docs.apertis.org/canterbury/canterbury/) | <https://gitlab.apertis.org/appfw/canterbury> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Application management and process control service | <https://gitlab.apertis.org/appfw/canterbury> |
- **Didcot**: Service which mediates file opening by media type (content type,
MIME type), URL opening by URL scheme, and other data sharing between user
applications.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Data sharing and file opening service | [Didcot API](https://docs.apertis.org/didcot/didcot/) | <https://gitlab.apertis.org/appfw/didcot> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Data sharing and file opening service | <https://gitlab.apertis.org/appfw/didcot> |
- **Newport**: It manages large downloads for applications and other services
running on the system (browser, email, other devices, etc).
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Download manager | [Newport API](https://docs.apertis.org/newport/newport/) | <https://gitlab.apertis.org/appfw/newport> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Download manager | <https://gitlab.apertis.org/appfw/newport> |
- **Barkway**: This service caters to the global UI, providing a popup
management framework, consisting of a user service and libraries that
interface with it.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Global popup management framework | [Barkway API](https://docs.apertis.org/barkway/barkway/) | <https://gitlab.apertis.org/appfw/barkway> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Global popup management framework | <https://gitlab.apertis.org/appfw/barkway> |
- **libseaton**: Provides interfaces to store persistent data. It is a shared
library using SQLite as the backend database.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Persistent data management library | [libseaton API](https://docs.apertis.org/libseaton/libseaton/) | <https://gitlab.apertis.org/hmi/libseaton> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Persistent data management library | <https://gitlab.apertis.org/hmi/libseaton> |
- **libclapton**: Library which is used for system information and logging.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Logging library | TBD | <https://gitlab.apertis.org/pkg/libclapton> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Logging library | <https://gitlab.apertis.org/pkg/libclapton> |
- **Ribchester**: The service responsible for managing the application and
services mount point and preparing the partitions based on the framework.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Application installer/mounting service | [Ribchester API](https://docs.apertis.org/ribchester/ribchester/) | <https://gitlab.apertis.org/pkg/ribchester> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Application installer/mounting service | <https://gitlab.apertis.org/pkg/ribchester> |
- **Rhosydd/Croesor**: Rhosydd and Croesor are system services for handling
access to sensors and actuators from applications. It provides a
vendor-specific hardware API to connect to the services which control the
hardware, and a SDK API for applications to use to access it.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Handling access to sensors and actuators | [Rhosydd API](https://docs.apertis.org/rhosydd/librhosydd-0/) | <https://gitlab.apertis.org/appfw/rhosydd> |
- | Sensor backend utilities | [Croesor API](https://docs.apertis.org/rhosydd/libcroesor-0/) | <https://gitlab.apertis.org/appfw/rhosydd> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Handling access to sensors and actuators | <https://gitlab.apertis.org/appfw/rhosydd> |
+ | Sensor backend utilities | <https://gitlab.apertis.org/appfw/rhosydd> |
- **Shapwick**: Shapwick is a platform component which monitors resource use.
It provides a system service and a library for communication with the
service.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Resource Monitoring | | <https://gitlab.apertis.org/pkg/shapwick> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Resource Monitoring | <https://gitlab.apertis.org/pkg/shapwick> |
@@ -402,26 +402,26 @@ Full package list in TSV format, categorized under different repository componen
- **libgrassmoor** : libgrassmoor is a library responsible for providing
media info and media playback functionalities
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Media information and playback library | [libgrassmoor API](https://docs.apertis.org/libgrassmoor/grassmoor/) | <https://gitlab.apertis.org/hmi/libgrassmoor> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Media information and playback library | <https://gitlab.apertis.org/hmi/libgrassmoor> |
- **Tinwell**: Is our Audio service. It focuses on complete audio handling
for the system and provides facilities to play, buffer, record audio
streams. It interacts with Canterbury to manage system audio
effectively when multiple audio sources are active.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Media playback service | [Tinwell API](https://docs.apertis.org/tinwell/tinwell/) | <https://gitlab.apertis.org/hmi/tinwell> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Media playback service | <https://gitlab.apertis.org/hmi/tinwell> |
- **Prestwood**: This service manages media and handles any activity related to
the removable media (such as mounting them), UPnP devices, etc and indicates
when they are ready for other services to communicate with them.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Disk mounting service | [Prestwood API](https://docs.apertis.org/prestwood/prestwood/) | <https://gitlab.apertis.org/hmi/prestwood> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Disk mounting service | <https://gitlab.apertis.org/hmi/prestwood> |
## Enabling components
@@ -473,9 +473,9 @@ Full package list in TSV format, categorized under different repository componen
such as a car GPS routing application, to share navigation and routing
information to third party applications.
- | Purpose | API Documentation | Git repository |
- |---------|-------------------|----------------|
- | Navigation and routing libraries | [Traprain API](https://docs.apertis.org/traprain/traprain-0/) | <https://gitlab.apertis.org/appfw/traprain> |
+ | Purpose | Git repository |
+ |---------|----------------|
+ | Navigation and routing libraries | <https://gitlab.apertis.org/appfw/traprain> |
## Enabling components
diff --git a/content/architecture/application-structure.md b/content/architecture/application-structure.md
index 18b5b7bf81a489d7c4ab88683facf6fa3b24ba0c..aa9532eb1ab353a93225d0057a384c148d7a5842 100644
--- a/content/architecture/application-structure.md
+++ b/content/architecture/application-structure.md
@@ -14,7 +14,7 @@ date = "2016-04-22"
+++
{{% notice warning %}}
-This documentation is written against version [16.12](https://wiki.apertis.org/16.12) of Apertis.
+This documentation is written against version 16.12 of Apertis.
This guide describes creating an agent using the
[Canterbury legacy application framework]({{< ref "canterbury-legacy-application-framework.md" >}}).
This framework is deprecated and therefore not recommended for new development.
diff --git a/content/concepts/application-entry-points.md b/content/concepts/application-entry-points.md
index 850e8477d04d1d435ca9ce3556884fc451e5b180..c91cbf2bd15f03959ff9dcd934dd08f2d890628b 100644
--- a/content/concepts/application-entry-points.md
+++ b/content/concepts/application-entry-points.md
@@ -756,7 +756,7 @@ Exec=/usr/Applications/org.apertis.Frampton/bin/frampton-control --shuffle-all
[Content hand-over]: {{< ref "content_hand-over.md" >}}
[Interface discovery]: {{< ref "interface_discovery.md" >}}
-[Apertis Application Bundle Specification]: https://appdev.apertis.org/documentation/bundle-spec.html
+[Apertis Application Bundle Specification]: {{< ref "bundle-spec.md" >}}
[Applications design document]: applications.md
[Application bundle metadata]: application-bundle-metadata.md
[Multimedia design]: multimedia.md
diff --git a/content/concepts/application-layout.md b/content/concepts/application-layout.md
index 075d1d8e9326eaf47a5dd3a6633a66b78ddc3c4b..63c714435456d6517bf27e4d06f2ce1f82e8fd96 100644
--- a/content/concepts/application-layout.md
+++ b/content/concepts/application-layout.md
@@ -107,7 +107,7 @@ functionality that is not necessarily long-term stable.
* The programs in application bundles may save variable data
(configuration, state and/or cached files) that are shared between all
[users][user] ([Applications design - Data storage]).
-* [Newport needs to be able to write downloaded files][bug 283] to a
+* Newport needs to be able to write downloaded files to a
designated directory owned by the application bundle.
* Because Newport is a platform service, its AppArmor profile will
need to be allowed to write to *all* apps' directories.
@@ -1312,7 +1312,7 @@ writing, no implementations of this idea are known.
<!-- Other documents -->
-[Apertis Application Bundle Specification]: https://appdev.apertis.org/documentation/bundle-spec.html
+[Apertis Application Bundle Specification]: {{< ref "bundle-spec.md" >}}
[Applications design]: {{< ref "applications.md" >}}
[Applications design document]: {{< ref "applications.md" >}}
[Applications design - Data storage]: {{< ref "applications.md#data-storage" >}}
@@ -1345,7 +1345,6 @@ writing, no implementations of this idea are known.
<!-- Other links -->
-[Bug 283]: https://bugs.apertis.org/show_bug.cgi?id=283
[Debian Policy §9.1 "File system hierarchy"]: https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1
[Filesystem Hierarchy Standard, version 2.3]: http://www.pathname.com/fhs/pub/fhs-2.3.html
[Filesystem Hierarchy Standard, version 3.0]: http://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html
diff --git a/content/concepts/applications.md b/content/concepts/applications.md
index c9dd22ecaa44a5e4b1192e7f50b8eea61b12066b..8c99591826b1a67572f2f8b86d798bce462d46fe 100644
--- a/content/concepts/applications.md
+++ b/content/concepts/applications.md
@@ -1353,13 +1353,13 @@ This document references the following external sources of information:
<!-- Other Apertis design documents -->
-[Apertis Application Bundle Specification]: https://appdev.apertis.org/documentation/bundle-spec.html
-[Application bundle metadata]: application-bundle-metadata.md
-[Application entry points]: application-entry-points.md
-[Application layout]: application-layout.md
-[Permissions concept design]: permissions.md
-[Public system extensions]: application-layout.md#public-system-extensions
-[Security]: security.md
+[Apertis Application Bundle Specification]: {{< ref "bundle-spec.md" >}}
+[Application bundle metadata]: {{< ref "application-bundle-metadata.md" >}}
+[Application entry points]: {{< ref "application-entry-points.md" >}}
+[Application layout]: {{< ref "application-layout.md" >}}
+[Permissions concept design]: {{< ref "permissions.md" >}}
+[Public system extensions]: {{< ref "application-layout.md#public-system-extensions" >}}
+[Security]: {{< ref "security.md" >}}
<!-- External links -->
diff --git a/content/concepts/infrastructure-maintenance-automation.md b/content/concepts/infrastructure-maintenance-automation.md
index a1404987fc32cdf82372ad4bbe98ed548ff0bd3f..fdc81f21e4aeaae2403b86cdcc527967ab7b7734 100644
--- a/content/concepts/infrastructure-maintenance-automation.md
+++ b/content/concepts/infrastructure-maintenance-automation.md
@@ -76,7 +76,7 @@ extend them to fully handle the complete branching process.
## Add test mode for current branching scripts
At the moment the quarterly release branching is done through a [set of
-scripts](https://gitlab.apertis.org/infrastructure/apertis-infrastructure/tree/apertis/v2020pre/release-scripts)
+scripts](https://gitlab.apertis.org/infrastructure/apertis-infrastructure/-/tree/main/release-scripts)
that get invoked manually by one the Apertis infrastructure team member
from their machine.
diff --git a/content/concepts/sensors-and-actuators.md b/content/concepts/sensors-and-actuators.md
index bd46ec314871c7b66fdef774f31840651962ba6a..1d5cfc1db32899f78be458da245a4a4088ab4251 100644
--- a/content/concepts/sensors-and-actuators.md
+++ b/content/concepts/sensors-and-actuators.md
@@ -1925,12 +1925,12 @@ the sensors and actuators SDK API ([Rhosydd]) with the latest W3C specifications
the [Vehicle Information Service Specification] API and the
[Vehicle Signal Specification] data model.
-It will also explain the required changes to align [Rhosydd] to the new W3C
+It will also explain the required changes to align Rhosydd to the new W3C
specifications.
## Rhosydd API Current State
-The current [Rhosydd API] is stable and usable implementing the
+The current Rhosydd API is stable and usable implementing the
[Vehicle Information Service Specification] and using the data model specified by
the [Vehicle Signal Specification].
@@ -1981,7 +1981,7 @@ JavaScript API.
## Rhosydd New Changes
- The [Vehicle Information Service Specification] API defines the Request and
- Response Objects using a JSON schema format. The [Rhosydd API] (both the
+ Response Objects using a JSON schema format. The Rhosydd API (both the
application-facing and backend-facing ones) has been updated to provide a
similar API based on idiomatic DBus methods and types.
@@ -2068,9 +2068,7 @@ enum Availability {
};
```
-[Rhosydd]: https://docs.apertis.org/rhosydd/index.html
-
-[Rhosydd API]: https://docs.apertis.org/rhosydd/index.html
+[Rhosydd]: https://gitlab.apertis.org/pkg/rhosydd
[Vehicle Information Service Specification]: https://www.w3.org/TR/vehicle-information-service/
diff --git a/content/concepts/system-updates-and-rollback.md b/content/concepts/system-updates-and-rollback.md
index 8c14fc71eab4d6b2f3aed1e596e9a3bea5bd6c31..0f261802362c695a5eecc38aa4bf80babc83c2ae 100644
--- a/content/concepts/system-updates-and-rollback.md
+++ b/content/concepts/system-updates-and-rollback.md
@@ -1011,7 +1011,7 @@ only upgrades created in the new branch.
## Command line HMI
A command line tool is provided to query the status using
-[the `org.apertis.ApertisUpdateManager` D-Bus API](https://gitlab.apertis.org/appfw/apertis-update-manager/blob/master/data/apertis-update-manager-dbus.xml):
+[the `org.apertis.ApertisUpdateManager` D-Bus API](https://gitlab.apertis.org/pkg/apertis-update-manager/-/blob/apertis/v2021/data/apertis-update-manager-dbus.xml):
```
$ updatectl
diff --git a/content/guides/ostree.md b/content/guides/ostree.md
index b2a5fd1c3c782ffbc474a3cad800f2bfe9184372..66fb988219c357356d7528f7789016b6e19f3adc 100644
--- a/content/guides/ostree.md
+++ b/content/guides/ostree.md
@@ -80,7 +80,7 @@ for instance to update SabreLite device manually to 18.12 release:
With 19.03 release Apertis is able to automatically detect the rollback
situation for incorrect upgrade and revert the system to the previous
state. More details are available in [manual test of
-rollback](https://qa.apertis.org/apertis-update-manager-rollback.html).
+rollback](https://qa.apertis.org/latest/apertis-update-manager-rollback.html).
# Updating the host with OSTree tool
diff --git a/content/policies/releases.md b/content/policies/releases.md
index 4d4ca52e3c32338ff2110f6e0e799f6175a6f07e..72c0f5440eaaf13582c1a9b74e429fdc1362a163 100644
--- a/content/policies/releases.md
+++ b/content/policies/releases.md
@@ -39,8 +39,8 @@ was previously known as "bug fixing freeze".
The final image is published on the release day.
If you need to request a break (exception) for any of the above freezes,
-you can do so by emailing the Apertis maintainers mailing list
-([maintainers@lists.apertis.org](https://lists.apertis.org/listinfo/maintainers))
+you can do so by emailing the Apertis mailing list
+([devel@lists.apertis.org](https://lists.apertis.org/listinfo/devel))
and getting the support of two or more Apertis maintainers.
## Releases
diff --git a/content/reference_hardware/minnowboard_setup.md b/content/reference_hardware/minnowboard_setup.md
index 2ddf3b1f78b6b77410e4af5770ac6fedd6e55766..3232f9f907bde48300cc223c80480cbf5bb73378 100644
--- a/content/reference_hardware/minnowboard_setup.md
+++ b/content/reference_hardware/minnowboard_setup.md
@@ -32,36 +32,37 @@ You may also have a:
### Setup instructions
-1. If the HSE (High Speed Expansion) is covered by a plate, you need to
- remove the plate.
-2. Download the amd64 UEFI target image (for example,
- [1](https://images.apertis.org/release/15.03/sac-15.03-amd64-target-amd64-uefi_150325-015101-collabora12.00.00.btrfs.img.gz)),
- plus the `.md5` and `.bmap` files (you can find them here,
- [2](https://images.apertis.org/release/15.03) or You might want a
- daily updated image. You can find it here as well
- [3](https://images.apertis.org/daily/)), and flash the image to a
- microSD card using command:
- sudo bmaptool copy path/to/image.img.gz /dev/mmcblk0
-3. Put the SD card in the board
-4. Plug in the serial cable (see
- [4](http://elinux.org/Minnowboard:MinnowMax#6-Wire_Serial_Console),
- pin 1 gets the black wire on common serial cables); connect to its
- kernel serial console using:
- screen /dev/ttyUSB0 115200
-5. Plug in the power supply and wait for it to boot
-6. On the **first boot**, the EFI shell might appear: type `bootx64` to
- get it to boot into grub2 (see
- [5](http://elinux.org/Minnowboard:MaxBoot#If_you_know_you_have_the_right_UEFI_setup_on_the_disk))
-7. If the board continues to boot into the EFI shell, the boot device
- order might be wrong (see
- [6](http://elinux.org/Minnowboard:MaxBios#Boot_Maintenance_Manager)).
- In the EFI shell, type `exit`, select the “Boot Maintenance
- Managerâ€, then “Boot Optionsâ€, then “Change Boot Order†and move
- “EFI Misc Device†(the microSD card) to the top of the list. Save
- and reboot. Also make sure that the EFI is 64-bit: type `exit` from
- the EFI shell and check that ‘X64’ is present in the version string
- (something like ‘MNW2MAX1.X64.0077.R01.1501291247’) at the top of
- the screen.
+1. If the HSE (High Speed Expansion) is covered by a plate, you need to
+ remove the plate.
+2. [Download]({{< ref "download.md" >}}) the Intel 64-bit (amd64) target image
+ and `.bmap` file.
+3. Flash the image to a microSD card using command:
+
+ sudo bmaptool copy path/to/image.img.gz /dev/mmcblk0
+
+4. Put the SD card in the board.
+5. [Plug in the serial cable](http://elinux.org/Minnowboard:MinnowMax#6-Wire_Serial_Console),
+ (pin 1 gets the black wire on common serial cables) and connect to its
+ serial console using:
+
+ screen /dev/ttyUSB0 115200
+
+6. Plug in the power supply and wait for it to boot
+7. On the **first boot**, the EFI shell might appear. Type `bootx64` to
+ get it to
+ [boot into grub2](http://elinux.org/Minnowboard:MaxBoot#If_you_know_you_have_the_right_UEFI_setup_on_the_disk).
+8. If the board continues to boot into the EFI shell, the
+ [boot device order might be wrong](http://elinux.org/Minnowboard:MaxBios#Boot_Maintenance_Manager).
+ - In the EFI shell, type `exit`
+ - Select the “Boot Maintenance Managerâ€, then “Boot Optionsâ€, then “Change Boot Order†and move
+ “EFI Misc Device†(the microSD card) to the top of the list.
+ - Save and reboot.
+
+{{% notice tip %}}
+Make sure that the EFI is 64-bit. Type `exit` from the EFI shell and check
+that ‘X64’ is present in the version string (something like
+`MNW2MAX1.X64.0077.R01.1501291247`) at the top of the screen.
+{{% /notice %}}
#### Touchscreen
diff --git a/content/release/15.12/releasenotes.md b/content/release/15.12/releasenotes.md
index 6c1fae1b8a27cd1626560c137ea08653d5f5e8f6..1a33e9df7682865326799d3df74efe334e6f5c3a 100644
--- a/content/release/15.12/releasenotes.md
+++ b/content/release/15.12/releasenotes.md
@@ -277,7 +277,7 @@ the user can see a live preview being updated, and after having provided
an edit message, they can publish their changes. They then get
redirected to the updated page, and a git commit is made to keep track
of their changes. A demonstration of this for the libgrassmoor
-documentation is available at <https://docs.apertis.org/>.
+documentation is available at `https://docs.apertis.org/`.
## UI Customisation design
diff --git a/content/release/16.03/releasenotes.md b/content/release/16.03/releasenotes.md
index cabed271c31ebf806896a303b6bb67add7454b54..aa0def0b9a4e0e8f03bfafe8c31fb013583429a1 100644
--- a/content/release/16.03/releasenotes.md
+++ b/content/release/16.03/releasenotes.md
@@ -373,9 +373,9 @@ the following table:
| | |
| -------------------------------------------------------------------------------------------------------- | ---------------- |
| **Package** | **Version** |
-| [image-utils](https://git.apertis.org/cgit/image-utils.git/log/?h=16.03) | 16.03 |
-| [apertis-image-customization](https://git.apertis.org/cgit/apertis-image-customization.git/log/?h=16.03) | 16.03 |
-| [linaro-image-tools](https://git.collabora.com/cgit/singularity/tools/linaro-image-tools.git/) | 2012.09.1-1co42 |
+| [image-utils]() | 16.03 |
+| [apertis-image-customization]() | 16.03 |
+| [linaro-image-tools]() | 2012.09.1-1co42 |
| parted, libparted0debian1 | 2.3-11ubuntu1co3 |
| python-debian | \>=0.1.25 |
diff --git a/content/release/16.06/releasenotes.md b/content/release/16.06/releasenotes.md
index a88873c26a783792cc46f13d735b758d87511a15..fbec13f4d12fb7e72502f78422f25f0eb23b3f82 100644
--- a/content/release/16.06/releasenotes.md
+++ b/content/release/16.06/releasenotes.md
@@ -111,7 +111,7 @@ remove, roll back and so on.
## Security design
Several potential improvements to the [Security concept
-design](https://docs.apertis.org/design/security.html) have been
+design]({{< ref "security.md" >}}) have been
collected from other automotive projects' security white papers, and
will be incorporated into the concept designs in future releases if time
permits. These include:
@@ -194,7 +194,7 @@ for future releases:
Rhosydd, an implementation of the non-vendor-specific and
non-product-specific parts of the [Sensors and Actuators concept
-design](https://docs.apertis.org/design/sensors-and-actuators.html), is
+design]({{< ref "sensors-and-actuators.md" >}}), is
available in Apertis 16.06.
## WebKit2GTK+
@@ -269,8 +269,8 @@ Starting in 16.03 all the Apertis specific packages (for example,
Mildenhall HMI) are automatically built in the Jenkins Continous
Integration system upon changes in `git` and are submitted to OBS on
success. During 16.06, this infrastructure was further improved and is
-now also applied to various [non-Apertis specific
-packages](https://git.apertis.org/cgit/packaging) which have Apertis
+now also applied to various non-Apertis specific
+packages which have Apertis
modifications (for example, AppArmor, D-Bus, GLib, Gtk, Pulseaudio and
systemd packaging).
diff --git a/content/release/16.09/releasenotes.md b/content/release/16.09/releasenotes.md
index 3a43f8f1f76a3f6528a1c80de38d6cfba5e472ee..c04d2c5ced85f860ddaa9d84a274e3e045c6bde8 100644
--- a/content/release/16.09/releasenotes.md
+++ b/content/release/16.09/releasenotes.md
@@ -52,7 +52,7 @@ them by estimated arrival time form the current location to help
choosing the one to book.
See the [Geolocation and navigation
-design](https://docs.apertis.org/geolocation-and-navigation.html) for
+design]({{< ref "geolocation-and-navigation.md" >}}) for
details.
### Hardware accelerated support for Web contents
@@ -72,7 +72,7 @@ and we plan to submit the remaining optimizations soon.
A new API (`org.apertis.Canterbury.AppDbHandler.LaunchAppPreferences`)
has been implemented to allow applications to launch their preferences
in `mildenhall-settings`, including
-[design](https://docs.apertis.org/preferences-and-persistence.html) and
+[design]({{< ref "preferences-and-persistence.md" >}}) and
support work, and unit tests for the implementation in Canterbury.
### Automatic debug packages
@@ -137,7 +137,7 @@ more efficient overall.
Various updates have been made to the list design (not yet released) and
to the [UI customisation
-design](https://docs.apertis.org/ui-customisation.html), to cover some
+design]({{< ref "ui-customisation.md" >}}), to cover some
new use cases and to clarify how the list (or roller) interacts with
adapters and with models, so that objects are stored once in a model,
and can be displayed in multiple views simultaneously without being
@@ -161,7 +161,7 @@ this is another step in that direction.
### Locale listing and switching
Minor updates have been made to the [internationalization
-design](https://docs.apertis.org/internationalization.html) to clarify
+design]({{< ref "concepts/internationalization.md" >}}) to clarify
the recommendation to use the [`systemd-localed` D-Bus
service](https://www.freedesktop.org/wiki/Software/systemd/localed/) for
determining and changing the system locale. Updates have been made
@@ -175,7 +175,7 @@ strings from ClutterScript files, which are used for UI design.
New packages have been added to the continuous integration loop, such as
`connman`, `appstream-glib`, `hotdoc`, `seed-webkit2`, `apertis-docs`,
and `apertis-designs`. See the [CI package
-list](https://git.apertis.org/cgit/apertis-customizations.git/tree/development/jenkins/apertis-build-packaging.yaml#n57)
+list](https://gitlab.apertis.org/pkg/apertis-customizations/-/blob/16.09/development/jenkins/apertis-build-packaging.yaml#L57)
for the complete listing.
### Updated packages
diff --git a/content/release/16.12/releasenotes.md b/content/release/16.12/releasenotes.md
index b5eecabf8fe39bda1f2c6aacc3368cac8b7ed520..4b24b7ef0f7456d802aa3eb4ff041ec07cd49572 100644
--- a/content/release/16.12/releasenotes.md
+++ b/content/release/16.12/releasenotes.md
@@ -40,7 +40,7 @@ but they can run on any UEFI-based x86-64 system. The `sdk` image is
### Stable application bundle layout
[Version 1.0.0 of the Application Bundle
-Specification](https://appdev.apertis.org/documentation/bundle-spec.html)
+Specification]({{< ref "bundle-spec.md" >}})
has been published, which means that the layout of bundles is now stable
and that bundles that adhere to it are guaranteed to be installable on
any future release of Apertis with no changes.
@@ -51,7 +51,7 @@ specification
### Web runtime
The first implementation of the [Web runtime
-specification](https://docs.apertis.org/latest/web-runtime.html) has
+specification]() has
landed in Apertis 16.12 as a technology preview. Application bundles can
use the `/usr/bin/bredon-0-launcher` shared launcher to exclusively rely
on HTML/JS/CSS for their needs while still being able to access all the
@@ -86,7 +86,7 @@ connect to it to run application bundles under an interactive debugger.
### Sample application bundles
The [source code for some simple application
-bundles](https://git.apertis.org/cgit/sample-applications/) has been
+bundles](https://gitlab.apertis.org/sample-applications) has been
released to demonstrate how to accomplish specific tasks, showcasing
different aspects of the SDK APIs provided in Apertis.
@@ -217,20 +217,20 @@ under review.
Traprain gained a new API allowing navigation services to send
turn-by-turn notifications and progress information about the current
journey accordingly to the [Geolocation and navigation
-document](https://docs.apertis.org/latest/geolocation-and-navigation.html#navigation-route-guidance-api).
+document]({{< ref "geolocation-and-navigation.md#navigation-route-guidance-api" >}}).
## Design
### Audio management
A first version of the [Audio management concept
-document](https://docs.apertis.org/latest/audio-management.html) has
+document]({{< ref "audio-management.md" >}}) has
been published, describing how streams and their priorities should be
managed in a Apertis system using PulseAudio.
### List widgets
-The [list concept document](https://docs.apertis.org/latest/list.html)
+The [list concept document]()
has been further clarified and it is now available for public
consumption, providing the architecture for modern, model-based advanced
list widgets, based on the experience gathered working with the roller
@@ -249,7 +249,7 @@ and dictation.
### Routing preferences handling in `nav:` URIs
The [Geolocation and navigation
-document](https://docs.apertis.org/latest/geolocation-and-navigation.html)
+document]({{< ref "geolocation-and-navigation.md " >}})
has seen the addition of routing-specific parameters in `nav:` URIs,
allowing applications to ask the navigation engine to plan routes for
specific kinds of vehicles, avoiding tolls and motorways, or trying to
@@ -258,7 +258,7 @@ pick the shortest or fastest route.
### Web runtime
New provisions have been added to the [Web runtime
-specification](https://docs.apertis.org/latest/web-runtime.html) to
+specification]() to
provide more details about the requirements that any compatible
implementation has to provide to be able to transparently run
applications that target the Apertis web runtime.
@@ -266,16 +266,16 @@ applications that target the Apertis web runtime.
### Web portal caching
A [document about caching in WebKitGTk+ and its usage in specific
-use-cases](https://docs.apertis.org/latest/web-portal-caching.html) has
+use-cases]({{< ref "web-portal-caching.md" >}}) has
been published, describing how a offline-first web portal could be
implemented using web technologies available in Apertis.
### Application layout
With the release of the [stable bundle
-specification](https://appdev.apertis.org/documentation/bundle-spec.html)
+specification]({{< ref "bundle-spec.md" >}})
the [Application layout
-document](https://docs.apertis.org/latest/application-layout.html) has
+document]({{< ref "application-layout.md" >}}) has
been updated to point to it and to provide more clarifications.
## Deprecations and ABI/API breaks
@@ -329,7 +329,7 @@ The old entry points discovery mechanism based on GSettings schemas is
still available but will be removed immediately after the release and
won't be available in 17.03. Use `.desktop` files to describe [entry
points in application
-bundles](https://appdev.apertis.org/documentation/bundle-spec.html#entry-points).
+bundles]({{< ref "bundle-spec.md#entry-points" >}}).
</dl>
diff --git a/content/release/17.12/releasenotes.md b/content/release/17.12/releasenotes.md
index 9a17d245df907c464c0ecad6f59a92eaaa5f1752..8dca01a2624928b6aa53e327e31b3eb09bfa6b74 100644
--- a/content/release/17.12/releasenotes.md
+++ b/content/release/17.12/releasenotes.md
@@ -49,7 +49,7 @@ regularly built set of images, focusing on the `minimal` variant.
### LXC template
A new [template script for
-LXC](https://git.apertis.org/cgit/apertis-image-recipes.git/tree/lxc/readme.md)
+LXC](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/-/blob/17.12/lxc/readme.md)
is now available to make instantiating LXC containers based on Apertis
as simple as possible: <code>
@@ -67,7 +67,7 @@ on `cb_build` has been replaced by new pipelines based on
[`debos`](https://github.com/go-debos/debos), which provides more
flexibility in customizing each image variant for the specific task at
hand and does so [with YAML-based
-recipes](https://git.apertis.org/cgit/apertis-image-recipes.git/tree/README)
+recipes](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/-/blob/17.12/README)
which are significantly easier to understand and modify than the
shell-based configuration setup used by the [previous
toolchain](https://git.apertis.org/cgit/apertis-image-customization.git/tree/).
@@ -85,7 +85,7 @@ the operating system from the writable runtime data.
Support for OSTree-based deployments is being progressively introduced.
OSTree repositories are currently [populated as a step in the new
image-building
-pipeline](https://git.apertis.org/cgit/apertis-image-recipes.git/tree/apertis-ostree-commit.yaml).
+pipeline](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/-/blob/17.12/apertis-ostree-commit.yaml).
The previously mentioned LXC containers templates already make use of
them, providing robust, autonomous upgrades to the instantiated
containers.
@@ -105,7 +105,7 @@ image variants.
### Merge-our-misc
-The [Merge-our-misc instance](https://mom.apertis.org/) feeding updates
+The Merge-our-misc instance feeding updates
from Ubuntu LTS has been reactivated and configured on a dedicated host.
## Design and documentation
diff --git a/content/release/18.06/releasenotes.md b/content/release/18.06/releasenotes.md
index df5ec937ded4f216da6d12d7c83c5e2455810e58..8ba188590ed3c9ee6ffa8314f15515b10e06e22f 100644
--- a/content/release/18.06/releasenotes.md
+++ b/content/release/18.06/releasenotes.md
@@ -156,7 +156,7 @@ To get them, replace the `.html` extension in the URL with `.pdf`, for
instance
[system-updates-and-rollback.html]( {{< ref "system-updates-and-rollback.md" >}} )
becomes
-[system-updates-and-rollback.pdf](https://designs.apertis.org/latest/system-updates-and-rollback.pdf).
+[system-updates-and-rollback.pdf](https://www.apertis.org/concepts/system-updates-and-rollback/system-updates-and-rollback.pdf).
### Improving storage and handling of the definitions and results of testcases
@@ -178,7 +178,7 @@ document based on the feedback gathered.
### Security aspects of OSTree
The [updates and rollback design
-document](https://designs.apertis.org/latest/system-updates-and-rollback.html%7CSystem)
+document]({{< ref "system-updates-and-rollback.md" >}})
has been updated to cover the security aspects of OSTree, describing how
updates are verified and how it relates to other technologies that can
be used in verified boot solutions.
diff --git a/content/release/18.09/releasenotes.md b/content/release/18.09/releasenotes.md
index d07a623d3b9be7a3558dbdb0e7a1107a03ca96c5..0715079ac94e3df1bb74cce409937728580a0ca2 100644
--- a/content/release/18.09/releasenotes.md
+++ b/content/release/18.09/releasenotes.md
@@ -116,7 +116,7 @@ different releases and conflicting dependencies. To overcome those
issues the [packaging jobs are now fully
dockerized](https://gitlab.apertis.org/infrastructure/apertis-jenkins-jobs/commit/59af079a3b),
using a [dedicated Apertis Docker
-image](https://gitlab.apertis.org/infrastructure/apertis-docker-images/tree/master/apertis-package-builder)
+image](https://gitlab.apertis.org/infrastructure/apertis-docker-images/-/tree/18.09/apertis-package-builder)
as their environment, bringing several advantages:
- each job runs in a separate container, giving more control of
diff --git a/content/release/v2019.2/releasenotes.md b/content/release/v2019.2/releasenotes.md
index 8c17061123dbb525782d4a176d58260bd1904183..44ada4e8cae815305d3cba45c9b9af4aaaeadd59 100644
--- a/content/release/v2019.2/releasenotes.md
+++ b/content/release/v2019.2/releasenotes.md
@@ -76,9 +76,9 @@ This release includes:
- the removal of the dependency on the `libquvi` package from
`totem-pl-parser` due to GPL-3 licensing issues
- the AppArmor profile for the `tracker` package has been [moved to the
- package itself](https://gitlab.apertis.org/pkg/tracker/commits/apertis/2.8.1-2co1),
+ package itself](https://gitlab.apertis.org/pkg/tracker/commits/apertis/2.1.8-2co1),
rather than in the `chaiwala-apparmor-profiles` package
- - the [switch to the ICU backend](https://gitlab.apertis.org/pkg/tracker/commits/apertis/2.8.1-2co4)
+ - the [switch to the ICU backend](https://gitlab.apertis.org/pkg/tracker/commits/apertis/2.1.8-2co4)
in the `tracker` package to avoid GPL-3 issues with `libunistring`
## Deprecations and ABI/API breaks
diff --git a/content/release/v2019dev0/releasenotes.md b/content/release/v2019dev0/releasenotes.md
index 3bfba00910b055e232ec0dcd14877e6370f6ba7c..03a5c333f3c7a37ee80e47992c05d05456a0d594 100644
--- a/content/release/v2019dev0/releasenotes.md
+++ b/content/release/v2019dev0/releasenotes.md
@@ -259,8 +259,7 @@ This has the advantage of allowing the SABRE Lite to boot from a common
armhf SD Card image, rather than one tailored specifically for the SABRE
Lite and aligns with the boot process used on ARM64 targets.
-A custom image (called
-[`uboot-v2019dev0-installer-mx6qsabrelite.img.gz`](https://images.apertis.org/release/v2019dev0/v2019dev0.0/installer/mx6qsabrelite-uboot/))
+A custom image (called `uboot-v2019dev0-installer-mx6qsabrelite.img.gz`)
is supplied with the v2019dev0 release that will flash U-Boot to the
EEPROM on SABRE Lite. This should be run on SABRE Lite boards that will
be used with v2019dev0.