Cutting a Release

Every 6 months, a new OmniOS stable release is made. Since it is not a frequent occurence, this page records the required tasks.

Update data

Before a release, the following data within illumos-omnios should be updated:

tzdata
PCI IDs

Ideally these should be upstreamed to illumos-gate too.

Create repositories

Create the new package repositories on the OOCE package server using the create_release script.

ooce# /pkg/create_release r151028
Creating release r151028 (28)
  core (omnios/core) @ 10028
  extra (extra.omnios/supplemental) @ 10228
  staging (omnios/core) @ 10128

pkg/server

Check pkg/server status

ooce# svcs '*/pkg/server:r151028*'
STATE          STIME    FMRI
online         12:55:22 svc:/application/pkg/server:r151028_core
online         12:55:24 svc:/application/pkg/server:r151028_extra
online         12:55:27 svc:/application/pkg/server:r151028_staging

nginx

Test the configuration and, if everything is ok, reload.

ooce# /opt/ooce/nginx-*/sbin/nginx -t
nginx: the configuration file /etc/opt/ooce/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/opt/ooce/nginx/nginx.conf test is successful
ooce# /opt/ooce/nginx-*/sbin/nginx -s reload

Test web browsing to the release, for example - https://pkg.omnios.org/r151028

Create branches

For each of the following repositories, create a branch for the new release - r1510nn - and create a PR to update the indicated files. Set up branch protection in github using the previous branch as a template