On 11/14/2013 03:55 PM, Matt Riedemann wrote:
On 11/14/2013 2:43 PM, David Ripton wrote:
On 11/11/2013 03:35 PM, David Ripton wrote:
I'll volunteer to do this release. I'll wait 24 hours from the
timestamp of this email for input first. So, if anyone has opinions
about the timing of this release, please speak up.
(In particular, I'd like to do a release *before* Matt Riedermann's DB2
support patch https://review.openstack.org/#/c/55572/ lands, just in
case it breaks anything. Of course we could do another release shortly
after it gets in, to make folks who use DB2 happy.)
Update:
There's now a "0.8" tag in Git but that release failed to reach PyPI, so
please ignore it.
Thanks fungi and mordred for helping debug what went wrong.
https://review.openstack.org/#/c/56449/ (a one-liner) should fix the
problem. Once it gets approved, I will attempt to push "0.8.1".
Any particular reason to go with 0.8 rather than 0.7.3 as a bug fix
release?
New maintainers, 2 years since a release, SQLAlchemy 0.8 compatibility
(we hope).
Even in projects that use strict semantic versioning, 0.x just means
"not ready yet." There are no stability guarantees until 1.0.
http://semver.org/ , point 4
--
David Ripton Red Hat drip...@redhat.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
