========
* Changed the ``db.setup`` arguments. It is now accepting a dictionary instead
of just a string to comply with the SQLAlchemy scaffold and this dictionary
should contain keys for the SQLAlchemy engine setup. There is another utility
that comes with Pyramid to setup the database under the `scripts` folder, it
is also working without any problem with stalker.db.
* The ``session`` variable is renamed to ``DBSession`` and is now a scopped
session, so there is no need to use ``DBSession.commit`` it will be handled
by the system it self.
* Even though the ``DBSession`` is using the Zope Transaction Manager extension
normally, in the database tests no extension is used because the transaction
manager was swallowing all errors and it was a little weird to try to catch
this errors out of the ``with`` block.
* Refactored the code, all the models are now in separate python files, but can
be directly imported from the main stalker module as shown::
from stalker import User, Department, Task
By using this kind of organization, both development and usage will be eased
out.
* ``task_of`` now only accepts TaskableEntity instances.
* Updated the examples. It is now showing how to extend SOM correctly.
* Updated the references to the SOM classes in docstrings and rst files.
* Removed the ``Review`` class. And introduced the much handier Ticket class.
Now reviewing a data is the process of creating Ticket's to that data.
* The database is now initialized with a StatusList and a couple of Statuses
appropriate for Ticket instances.
* The database is now initialized with two Type instances ('Enhancement' and
'Defect') suitable for Ticket instances.
* StatusMixin now stores the status attribute as an Integer showing the index
of the Status in the ``status_list`` attribute but when asked for the value
of ``StatusMixin.status`` attribute it will return a proper Status instance
and the attribute can be set with an integer or with a proper Status
instance.