On 11/20/07, Kumar Gala galak@kernel.crashing.org wrote:
On Nov 20, 2007, at 7:41 AM, Wolfgang Denk wrote:
Hello to everybody...
...who has sumbitted new patches without waiting for the official opening of the new merge window.
Please note that I will NOT apply any of these patches yet. And I recommend all custodians to wait, too.
The plan is as follows:
Grant Likely's patches come first, then comes the drivers reorgani- zation, and I tend to say that's what goes into 1.3.2 - after such a significant restructuring I'd rather want to have it tested and cleaned up first before adding more new stuff. Let's do a quick cycle for 1.3.2 (which would be also good to bring us back in sync with the Linux cycle).
In any case, after that probably all patches have to be rebased against the new tree - otherwise we would run into a lot of nasty merge conflicts.
How long will that mean in terms of taking any actual new code between when the merge window closed for 1.3.0 and the 1.3.3 or 1.4.0 window opening? Seems like it will be a very long time.
My patches are ready to be pulled and merged by Wolfgang now. The rebase/merge that everyone will need to do is to ease the pain of the Makefile changes. It's the sort of fixups that are a lot easier if the custodians do them rather than Wolfgang having to figure it all out.
I wouldn't be surprised if the new merge window should be openable in less than a day. The next question is how long should the window be open?
Cheers, g.