diff options
| -rw-r--r-- | Release-engineering.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/Release-engineering.md b/Release-engineering.md index 0c80eed..3d7853c 100644 --- a/Release-engineering.md +++ b/Release-engineering.md @@ -1 +1,8 @@ -The February ISO was the last official release, which supports the i686 architecture, so we need to create monthly(?) ISOs on its own. Until 2017 November, we can use the official i686 repository to build the ISO. The task is simple: we can use the official [archiso](https://git.archlinux.org/archiso.git/) tool to procedure ISO images. After [this change](https://lists.archlinux.org/pipermail/arch-releng/2017-January/003763.html) is committed, we simple need to replace `x86_64` with `i686`, and run the command with the default configuration, which will procedures a working i686 ISO hopefully. If further customization is needed, then we could create a git repository for our archiso configuration.
\ No newline at end of file +The February ISO was the last official release, which supports the i686 architecture, so we need to create monthly(?) ISOs on its own. +Until 2017 November, we can use the official i686 repository to build the ISO. +After that, we simply switch to our own i686 repository. +The generation of the iso is simple: +We forked [archiso32](https://github.com/archlinux32/archiso32) from the official [archiso](https://git.archlinux.org/archiso.git/) tool to produce ISO images. +After [this change](https://lists.archlinux.org/pipermail/arch-releng/2017-January/003763.html) was committed, we simply skipped all commits related to the removal of i686 support. +Possibly we may drop support for `x86_64` to get smaller images which fit on a standard cd. +We then run the command with the default configuration, which will produce a working i686 ISO hopefully.
\ No newline at end of file |