Hi all,

I want to know Linux Kernel Release Schedule.
I know the next is 2.6.28-RC1 is planned to release. But on what date ?
When is 2.6.28 is planned to release ?

I believe this has to be planned very well. I just want to know how one can know about this plan ........... I looked on Google but not getting even good pointers.........

It's still "whenever its ready". Work continues until Linus decides that remaining problems do not affect a large number of users or are at least trivial to fix. Then the RC1 comes out and testing/repatching happens and the same story until RCN. If Linus is very happy, the code goes to full release. Initially Linus hoped this process would always take the same amount of time, but for the past year he has regularly been about 4 weeks late on his preferred schedule. For more definitive informations, see: http://kernelnewbies.org/

When it is ready.

But there are usually about 4-5 releases in a year.
http://ldn.linuxfoundation.org/artic...ent-april-2008
(Funny, I'd have though it would be in a FAQ someplace...)

Yeah I understand "in theory" part...
But, my question is in any way
Does Linus declare that xyz is expected date for 2.6.28-RC1 OR in different words, how do all developers decide that my LAST date to submit the patch is XYZ and so I have to complete my Dev work before this date.........

Quite understandably, Linus can not wait for every developer to finsh off his work... Only Linus has to declare that Window is open to submit patch and ok now NO more changes....

I believe that it happens in this way and if it happens this way.... He must be declaring all those things Publicly such that every1 is aware........... If so how and on what web site or on what mailing list ?

That's not how it works - did you read any of the links you were directed to?

Linus has been known to make a press statement about when a new release becomes available. It will also be announced on the mailing lists. So - subscribe to he mailing lists.

Patches are always considered. The timing of the patch is not critical, as it will take Linus a while to get around to it anyway. A lot of good patches fail to make particular releases just from the workload.

When the next release is out, you can start patching against that. Nobody expects the professional - do it by the deadline - approach. Submit the patch when you think it's ready for inspection. Make sure your kernel source tree and all your tools are to date. Throw out what you learned in school about such disciplines, it's a different environment. Though you will get enough notice so you can hammer a patch into submission in time - if it has already been accepted. If it hasn't been accepted, relax. Just do it - when you want to, go to it.

Thanks...
I went thru some mailing list and i think i hv got wht i wanted to know....

thanks again all