after today's meeting, I think we have a reasonable plan for how to get releases going:
we release swift with a changelog mentioning that deployers shoudl upgrade libec. then we also release pyeclib with a warning if libec<1.3.1. then after libec is in distros, roll those hard requirements forward through the dep chain
The last thing I'd like to see before we open this bug is a script (or process) to point people to that gives a mechanism to move existing at-risk data to a safe configuration.
after today's meeting, I think we have a reasonable plan for how to get releases going:
we release swift with a changelog mentioning that deployers shoudl upgrade libec. then we also release pyeclib with a warning if libec<1.3.1. then after libec is in distros, roll those hard requirements forward through the dep chain
...from http:// eavesdrop. openstack. org/meetings/ swift/2016/ swift.2016- 11-16-21. 00.log. html
----
The last thing I'd like to see before we open this bug is a script (or process) to point people to that gives a mechanism to move existing at-risk data to a safe configuration.