Vera

**vera 1.0.0** builds on the [second beta](https://github.com/wq/vera/releases/v1.0.0b2) with a couple of improvements for compatibility with the final releases of [wq.db 1.0](https://github.com/wq/wq.db/releases/v1.0.0) and [Django Data Wizard 1.0](https://github.com/wq/django-data-wizard/releases).

Changes since vera 1.0 beta 2

* Leverage the new [cache option](https://wq.io/docs/pagination-and-caching) in wq.db (79e58ca, fdc1dd3).
* Invert the relationship between vera and the Django Data Wizard (73e992f, see https://github.com/wq/django-data-wizard/issues/3). Where as the wizard formerly depended on vera, vera now depends on the wizard and implements four wizard templates (serializers), as described in the [updated documentation](https://github.com/wq/verabulk-data-import).

**vera 1.0 beta 2** brings a project reorganization to work around issues with swappable models and migrations (see wq/django-swappable-models12). The models have been grouped into three apps without default migrations. Once you have determined which models you want to override (if any), run `./manage.py makemigrations` to have the appropriate vera migrations generated for you.

The models have been renamed as follows:

| Old Name | New App | New Name | Notes |
| --- | --- | --- | --- |
| `vera.Site` | `vera.params` | `params.Site` | `BaseSite` is now an [IdentifiedModel](https://wq.io/docs/identify). |
| `vera.ReportType` | `vera.params` | `params.ReportType` | |
| `vera.Parameter` | `vera.params` | `params.Parameter` | |
| `vera.Event` | `vera.series` | `series.Event` | |
| `vera.Report` | `vera.series` | `series.Report` | |
| `vera.Result` | `vera.results` | `results.Result` | A new `ValueValidator` automatically checks `Parameter.is_numeric` |
| `vera.EventResult` | `vera.results` | `results.EventResult` | |

The old models (and their base implementations) can be accessed from `vera.base_models`:

python
from vera.base_models import BaseSite
class MySite(BaseSite)
...

settings.py
WQ_SITE_MODEL = "myapp.MySite"


The `vera.models` module now serves as a shortcut to access the currently active version of each of the seven models.

python
from vera.models import Site
from myapp.models import MySite
assert(Site == MySite)


Be sure to update your settings:

diff
INSTALLED_APPS = (
- "vera",
+ "vera.params",
+ "vera.series",
+ "vera.results",
)

**vera 1.0.0b1** is the beta version of the upcoming 1.0 release of [vera](https://wq.io/vera). The main focus of this release is compatibility with the upcoming [wq.db 1.0 release](https://github.com/wq/wq.db/releases/) and the new standalone [natural-keys library](https://github.com/wq/django-natural-keys).

**[vera](https://wq.io/vera) 0.8.0** brings a number of updates and breaking changes for compatibility with [wq.db 0.8](https://github.com/wq/wq.db/releases/).

Some highlights from the wq.db release notes:
- Compatibility with Django 1.8 and Django REST Framework 3
- The charting API has been changed to take advantage of [Django REST Pandas 0.4.0](https://github.com/wq/django-rest-pandas/releases/tag/v0.4.0).

Be sure to view the release notes for wq.db and Django REST Pandas to see what changes to make in your project.

**[vera](http://wq.io/vera) 0.7.0** brings Python 3 & Django 1.7 compatibility, and (more significantly) the transition from a [wq.db](http://wq.io/wq.db) `contrib` module to a full PyPi package (see wq/wq.db29). The API is the same, but instead of:

python
from wq.db.contrib.vera.models import BaseEvent


You can just do:

python
from vera.models import BaseEvent


The full history of the wq.db version of vera has been merged into this repository. In addition, the vera-specific components of [wq.db chart](http://wq.io/docs/chart) have been moved to here (see 5ed6317 and https://github.com/wq/wq.db/commit/8368e8898af1f82a140ef0c8dc8a65c3c41c2dd0 ).

Be sure to check out the updated [readme](http://wq.io/vera) for new documentation on the models included in vera.

Seventh release of vera, included in [wq.db 0.6.2](https://github.com/wq/wq.db/releases/tag/v0.6.2).