> 3. Feature branches are expected to add a file to upgrading/next that > explains their upgrade requirements.
I'm wondering whether we would want this file to exist even if the feature has no upgrade requirements, and maybe just say "no upgrade requirements" -- so that the difference between "we thought about it and this feature has no upgrade requirements" and "we didn't think about it" is clear both at review time and in retrospect during release. ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/Taa08486771d9b334-Me341f1efe279bb126afa26c7 Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
