We've noticed files overwriting themselves on migration. If you're importing two files, one named a/1.jpg and another named b/1.jpg, the basename() for both these are 1.jpg even though they are different files in different directories.

We always assume that mail sends successfully, so when it fails, we give the user confusing messages.

If you have multiple Drupal installations that share common data, it would be nice to redirect queries any database server without much work. db_prefix only works with different databases or tables on the same server. This issue is to allow multiple servers.

MongoDB collections can be capped, even though we haven't added the UI for it yet #660460: Watchdog: Support Capped Collections, just go into the mongo shell:

While I can't point to any core bug this causes, and this can be solved in contrib, I think that we should save and restore the current working directory because this is a known problem with register_shutdown_function (see comments in thread) and a potential hazard for many people.

We ran into a case this weekend, where watchdog grew to 116G+. While the exact cause still isn't known, it seems possible that an errant watchdog() call could of passed large arrays in the variables, and that these arrays were written to mongo.

When we display the watchdog record, the user object is passed to theme_username, and with the core implementation, all we really need is name (and maybe uid and maybe homepage). Attached patch saved user.uid and user.name, and then when loading tries to get the rest of the object, in-case theme_username needs it.

Development methodologies weren't taught at Cornell when I took Computer Science 1982-1986. I first remember hearing about them in the early 1990's. At CivicActions, we've talked about "agile" and "scrum" for some time. But it really took the last couple of projects for me to embrace these methods.

It sounds pretty obvious. My php warning to you is: