To follow up one of the points brought up in the fuel-plugins [1] session. We briefly discussed using reno [2]. The system appears to be quite clean and concise and will work for this need, and should work for general release notes. I'd propose that we start using reno to catalog changes to the plug-in interfaces and encourage usage elsewhere. I'd like to start a discussion about this further. [1] https://etherpad.openstack.org/p/austin-summit-fuel-plugins [2] http://docs.openstack.org/developer/reno/ -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160503/20d5de24/attachment.html>