Release Engineering for pkgsrc
Thomas Klausner <wiz@NetBSD.org>
pkgsrc usage
- Tracking -current (always the latest)
- Stable branches (stable & security bugs fixed)
How are stable branches created?
- quarterly
- preceded by "freeze" period
Freeze
- usually two weeks
- reduced updating
- concentrating on build fixes
- and closing PRs!
Freeze end
- cut branch (in CVS)
- release announcement (mail, www)
- localsrc/releng/releng-pkgsrc
Binary packages
- NetBSD: dedicated build hosts for amd64/i386
- binaries on nbftp
- other platforms volunteer effort :(
branch maintenance
- security fixes
- rarely other fixes (build)
- four eyes principle
- must be requested by developers!
how to request pullups
- Easy!
- look at diff to branch
- test on branch, if possible
- forward commit message(s) to pullup-pkgsrc
pullup-pkgsrc needs manpower
- while not critical,
- a couple more people would be great