Explanation of branches for NetBSD releases

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Date: Sunday, October 30, 2005 - 10:39 pm

As previously spelled out in some detail all major NetBSD releases now have a
an additional branch created after their release for the tracking of
security and critical updates.

Examples: (where branches refer to CVS branch names)

Release Main Branch Security/Critical Branch
------- ----------- ---------------
NetBSD 2.0 netbsd-2 netbsd-2-0
NetBSD 2.1(*) netbsd-2 netbsd-2-1(*)
NetBSD 2.2(+) netbsd-2 netbsd-2-2(+)
NetBSD 3.0(*) netbsd-3 netbsd-3-0(*)
NetBSD 3.1(+) netbsd-3 netbsd-3-1(+)

* - upcoming releases
+ - possible future releases

There are currently insufficient resources to do full binary releases of
each security/critical branch as they grow on each main branch.

Therefore, on an ongoing basis all security/critical branches will be under
full source level support for each support main branch. In addition the
most recent security/critical branch will have binary updates published
as well.

This means only the latest security/critical branch (for instance 2.1.1 once
2.1 releases) will have binary updates published for them. All other branches
(today 2.0.x) will have source changes applied only. These branches will
appear as occasional builds in the NetBSD daily area on ftp.netbsd.org but
no other binary releases will be done for them.

For any further clarifications and/or questions please feel free to contact
the NetBSD Release Engineering team at releng@netbsd.org

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
NetBSD Security Advisory 2007-006: Local panics in display d..., NetBSD Security-Officer, (Thu Sep 13, 5:56 pm)
Preparing for Summer of Code 2009, Jan Schaumann, (Mon Feb 2, 12:17 pm)
New Developers, grant beattie, (Sat May 31, 11:34 am)
NetBSD Security Advisory 2008-002: Endianness issue in fast_..., NetBSD Security-Officer, (Thu Feb 28, 7:36 pm)
Announcing the NetBSD Project Blog, Mark Weinem, (Sun Apr 26, 6:09 pm)
New Developers, Jan Schaumann, (Sun Feb 1, 3:12 pm)
NetBSD Security Advisory 2008-009: BIND cache poisoning, NetBSD Security-Officer, (Thu Jul 24, 8:15 pm)
Announcing the pkgsrc-2004Q4 Branch, Alistair Crooks, (Tue Dec 21, 1:35 pm)
Summer of Code applications period started, Jan Schaumann, (Tue Mar 25, 1:21 am)
Regular daily builds, James Chacon, (Mon May 2, 1:31 pm)
NetBSD Security Advisory 2005-002: Local DoS via audio devic..., NetBSD Security-Officer, (Thu Jun 30, 6:12 pm)
New NetBSD Core Team, Alistair Crooks, (Wed Aug 3, 2:10 am)
Explanation of branches for NetBSD releases, James Chacon, (Sun Oct 30, 10:39 pm)
NetBSD Security Advisory 2006-005: bridge memory disclosure, NetBSD Security-Officer, (Wed Mar 29, 9:31 pm)
NetBSD Security Advisory 2006-013: sysctl(3) local denial of..., NetBSD Security-Officer, (Wed Apr 12, 10:34 pm)
ftp.netbsd.org downtime Sat, June 29, 9am Pacific time, Michael Graff, (Fri Jun 28, 4:02 am)
Announcing the pkgsrc-2006Q2 Release, Alistair Crooks, (Sun Jul 2, 9:27 am)
Announcing the start of the NetBSD 4.0 release process, Jeff Rizzo, (Fri Aug 25, 10:44 am)
NetBSD Security Advisory 2009-005: Plaintext Recovery Attack..., NetBSD Security Officer, (Tue Jul 14, 5:33 pm)
NetBSD Security Advisory 2008-012: Denial of service issues ..., NetBSD Security-Officer, (Mon Sep 15, 5:03 pm)