New answers tagged changes
You should have continuous deployment procedure to some sort of library repository which has unit tests integration tests maybe a review for the release
You should keep a "software migration document" describing the new design and teaching how to migrate existing software. It should answer these questions: what changed? how do I update my code? why did this change happen? [optional] where can I learn more? Possibly it should be short, friendly, informative (with references to further documentation). ...
Top 50 recent answers are included