Open Stack

Sorry for the delay. django-openstack-auth 1.1.7 was released last Friday and
it seems David forgot to update global requirements.

Now let me clarify how to handle this kind of bugs which requires a
fix in a library after the release.
What is the appropriate way to fix a bug depending on libraries
(including internal and external libraries) after the release.
Can we mark the bug as "Fixed" even if operators use a newer released
version of libraries is used?
In this case the bug itself is not fixed without upgrading the libraries,
but we cannot update the requirement after the release in general.
Another way is to copy the logic from a library a workaround but it is
a bit ugly.
Of course we need to keep compatibility for the declared version in
requirement.txt.

Thanks,
Akihiro


On Tue, Sep 23, 2014 at 6:47 PM, Thierry Carrez <thierry at openstack.org> wrote:
> Akihiro Motoki wrote:
>> I would like to request dependency freeze exceptions for django-openstack-auth.
>> https://review.openstack.org/#/c/123101/
>
> This arguably counts as an internal library. We are freezing those now
> (well, last Friday was the deadline), so +1 on this one.
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Akihiro Motoki <amotoki at gmail.com>