| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 21 May 2008 16:08:37 +0300 From: Tarkan Erimer <tarkan@...one.net.tr> To: lkml <linux-kernel@...r.kernel.org> Subject: Suggestion About Kernel Releases Hi, After long discussions about kernel release methodology, an idea has came to ( Any comments welcomed :-) ) my mind : - 2 weeks of merge window for each "rc" releases should remain the same . - When decided the 2.6.xx-rcx is ready to become 2.6.xx, it should be 2.6.xx-test1 instead of 2.6.xx - Chris Wright (or whoever will handle these "testX" maintaining) can maintain these "testX" releases as like 2.6.x.y maintaining. - After releasing the "testX" releases, the new kernel release process should start. - When Chris decided it is stable enough, it should release as 2.6.xx (stable). - Of course, 2.6.x.y releases follows then as usually. Please share your opinions. Thanks :-) Tarkan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists