Files
orrisroot a033dfa970
Validate / lint (push) Successful in 11m0s
Validate / import-test (push) Canceled after 1m12s
feat: bootstrap Zabbix template repository
Set up a repository for custom Zabbix templates and add the first
template for Dell PowerVault ME storage systems.

- Add conventions, version policy, and release documentation.
- Add validation, index, packaging, export, and import-test scripts.
- Add a disposable Zabbix test stack with version-aware imports.
- Add PowerVault ME SNMP exports for Zabbix 7.0 and 8.0.
- Cover system information, unit health, sensors, ports, and
  firmware revisions.
2026-11-03 14:40:19 +09:00

49 lines
1.0 KiB
Markdown

# Release Process
## Checklist
1. Update `CHANGELOG.md`.
2. Update `version` in `manifest.yaml`.
3. Confirm that `make lint` passes.
4. Confirm that `make import-test` passes.
5. If an 8.0 export exists, run `make import-test` with the 8.0 image tags (see [versioning.md](versioning.md)).
6. Run `make index` to update the template list in `README.md`.
7. Commit the changes.
8. Tag the release per template.
9. Run `make package` and attach the zips to the release.
```bash
make lint
make import-test
make index
git add .
git commit -m "apache: add HTTP template"
git tag app-apache-v1.0.0
make package
```
## Artifacts
`make package` creates zips in `dist/` using the following naming pattern.
```text
dist/app_apache-1.0.0-zbx7.0.zip
dist/app_apache-1.0.0-zbx8.0.zip
```
Zip contents:
```text
README.md
CHANGELOG.md
manifest.yaml
template_app_apache.yaml
assets/...
```
The `dist/` directory is not tracked by Git. Attach the zips to a release page or upload them to a file server.
## Versioning
See [versioning.md](versioning.md).