[Back before we were public I used to send out semiregular status reports, but Darin pointed out I can now send them here.]
http://code.google.com/p/chromium/issues/list?q=os:linux is hopefully up to date with what everyone's working on. Please feel free to bring other Linux-specific bugs to my attention. We've had a bunch of contributions from people outside Google, which is pretty rad. I believe we [people working on Linux] are currently kind of bottlenecked on the WebKit merge: there's little point in making our local copy of WebKit code portable when those changes have been made upstream already. The merge is especially gnarly this time because we've been tracking the stable Safari 3.1 branch of WebKit the past few months and now we're trying to switch to trunk, and simultaneously we've been trying to push upstream as much of our forked code as reasonable. To that end, Tony has been helping with the merge; last I heard they've finally got all the compiler warnings fixed and are just down to 4,200 linker errors. ;) If you want to help out with that, try asking on the (temporary) channel #chromium-merge on freenode. Unfortunately, testing changes done for the merge currently requires Windows, so maybe it'll be hard to help if all you have is Linux. On the other hand, hopefully this will be done soon, and once the port is a bit more flushed out future merges can be done on your platform of choice. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
