On 20.1.2012 18:58, Freddie Cash wrote:
It cannot be merged into RELEASE! RELEASE is a point on a branch,
as soon as RELEASE had been released, you can't push anything into
it, unless you have a time machine.
I think he's asking "what's the criteria to push a patch to
RELENG_8_2, the security/fixes branch of -RELEASE?" IOW, how does one
increase the patch level (8.2-RELEASE-p5 -> 8.2-RELEASE-p6, etc) of a
release?
I believe, and RE/security team can correct me on this, that the
criteria is along the lines of "security issues and major bug fixes
only". Perhaps that policy should be looked at and loosened slightly
to also include "driver updates"? Or something along those lines?
Perhaps look at releasing point releases (8.2.1) like DoubB suggested?
I have already said it in this thread - I believe we should consider
issuing much more errata notices (i.e. -pX); with that I mean we should
consider more bugs as "major bugs". I don't really see a reason why not.
And we should also provide some mechanism to allow for cherry-picking
individual errata notices to be applied on the given release (e.g. p1,
p2, p5, but not p3, p4).
I don't think it makes sense to issue errata notices for driver updates
as in support for new devices because we don't ship installation media
with these patches applied. In those cases we would need to make those
"point" releases. On the other hand, simply releasing minor releases
more often would solve that problem too.
--
S pozdravom / Best regards
Daniel Gerzo, FreeBSD committer
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
