Files outside the LP tree reference LP code

[Henning Eggers]

The prime example for this is +inbound-email-config.zcml which is not part of the LP tree or lp-production-configs but references code in the LP tree. When that code's location changed, the server startup broke over that zcml file. The LP devs could not anticipate this because 1) most of them do not know about the file 2) it won't get caught by a "grep" because it is not inside the tree.

The other problem with +inbound-email-config.zcml is that it can not be be safely changed without downtime. That makes the handling a real hassle because any change that affects it will have to leave both the old and the new location in the tree, only to remove the old location after the downtime (usually the roll-out). That is annoying.

We need a better solution for files outside the LP tree that reference LP code so that they are not missed when code is updated.

[Gary Poster (gary)]

This particular example could be improved. However, the fact that our production configuration is private makes other aspects of this potentially tricky. Perhaps they could be included like shipit is now.

[William Grant (wgrant)]

A change to +inbound-email-config.zcml caused a production incident this morning, breaking loganberry scripts. Having this file inside the versioned directory would have avoided the mess.

Other private configuration is stored sanely in lp-production-configs. Why can't this be?