We'll definitely need to put out a release of that. That's largely ready to go, but we haven't finished the work to let evolutions and migrations co-exist yet.
Do you know the failure you hit, specifically? Djblets doesn't have a direct package dependency on django-evolution.

It was an error in ez_setup, something about catching an exception using the old style (ExceptionName, e). It seemed like this commit would fix it.
django_evolution>=0.7.6 is listed in dev-requirements.txt and I assumed that was what brought it in.
I actually wanted to test reviewboard with python 3, but ran into problems with the apps having duplicate labels (the admin app) and once I thought I had fixed that there was some other error about the apps not being initialized. So I guess I'll have to wait a bit longer before trying python3...

There's still a lot to sort out. It's not Python 3 that's causing issues with the apps, but rather newer versions of Django (which Review Board requires if using Python 3, as Django 1.6.x is not compatible with Python 3.4+). We've been inching our way toward getting everything running on Python 2.7/3.5-3.7 with Django 1.11 (with the goal to then move to Django 2.x and Python 3.5+ only), but there's still a lot of tasks for that, and many other tasks that have pulled me away from this work. I have some time penciled in for this soon.