When good code is not enough: Lessons learned maintaining modules

Arlina Espinoza Rhoton

We are all good developers. At least we think we are. Our code works, it's performant - oh, and it's elegant. So let's deploy that new release for our module. Wait, 10 issues are reporting that our new release broke their site? What went wrong?

In this session I'll share my experience helping maintain the Apigee suite of modules and other projects. This includes thinking about upgrade paths, backwards compatibility, documentation and testing. Tips shared will be useful for anyone maintaining modules, installation profiles, or deployment scripts.

Drupal is a registered trademark of Dries Buytaert.