I have notice today, that sys-kernel/hardened-sources-3.15.5-r1 has been marked stable. Long discusion short: Kernel 3.15.5 is marked stable by kernel.org - OK Grsec grsecurity-3.0-3.15.5-201407142248 - for testing purpose Stable Kernel + Grsec for testing version shall not be marked as stable IMO. Stable Kernel + Stable Grsec shall be marked as stable kernel. Its cool and useful to have latest stable kernel with latest grsec-test, but IMO it shall not be considered stable. Since this can turn into long pointless discusion I'm suggesting this small workaround. If someone merge hardened-sources, w/o stable grsec, print warning... "Latest stable Grsec is in hardened-sources-3.14.13-r1. %Kernel% you are about to merge has Grsec test patch %version%."
(In reply to tomas charvat from comment #0) > I have notice today, that sys-kernel/hardened-sources-3.15.5-r1 has been > marked stable. Long discusion short: > Kernel 3.15.5 is marked stable by kernel.org - OK > Grsec grsecurity-3.0-3.15.5-201407142248 - for testing purpose > > Stable Kernel + Grsec for testing version shall not be marked as stable IMO. > Stable Kernel + Stable Grsec shall be marked as stable kernel. > > Its cool and useful to have latest stable kernel with latest grsec-test, but > IMO it shall not be considered stable. > > Since this can turn into long pointless discusion I'm suggesting this small > workaround. > If someone merge hardened-sources, w/o stable grsec, print warning... > "Latest stable Grsec is in hardened-sources-3.14.13-r1. %Kernel% you are > about to merge has Grsec test patch %version%." For as many people as would agree with you, there are as many who would disagree. I'm not entering ths arena.
