|
[20041220]
|
Rumour: Introducing "security update" releases
I hear there will be a change in the NetBSD release model to accommodate
security fixes e.g. from Security Advisories (SAs). Besides major
releases (1.5, 1.6, 2.0, 3.0, ...) and minor/bugfix releases (1.6.1,
1.6.2, 2.1, 2.2, ...) there will now be 'security releases', which are
the last major/minor release + security patches only (in contrast to
the changes on the 'stable' branch, which also include minor feature
enhancements). These security releases will be named after the last
major/minor release and indicate the difference by a third number,
e.g. one that fixes this compat thing for 2.0 would be 2.0.1 when
another SA comes out before 2.1, it will be in 2.0.2 and so on,
and once 2.1 is out the door security releases will be 2.1.1, 2.1.2,
etc.
These security releases are intended to provide upto-date binaries for
people who run production systems and depend on fixed problems
but who do not intend to deal with the source updating, building
and possible troubles arising from using the stable branch.
(Please note that I just hear this, I'm not one of the people
deciding these things!)
[Tags: releases, Security]
|