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
--
