django-river | Django Ecosystem Directory

Bot releases are hidden (Show)

django-river - 0.6.1

Published by javrasya about 8 years ago

Bug - After content_type and field are moved into ProceedingMeta model from Transition model in version 0.6.0, finding initial and final states was failing. This is fixed.
Bug - 0002 migrations was trying to set default slug field of State model. There was a unique problem. It is fixed. 0002 can be migrated now.
Improvement - The way of finding initial and final states is changed. ProceedingMeta now has parent-child tree structure to present state machine. This tree structure is used to define the way. This requires to migrate 0003. This migration will build the tree of your existed ProceedingMeta data.

django-river - 0.6.2

Published by javrasya about 8 years ago

Bug - Migration 0002 and 0003 were not working properly for postgresql (maybe oracle). For these databases, data can not be fixed. Because, django migrates each in a transactional block and schema migration and data migration can not be done in a transactional block. To fix this, data fixing and schema fixing are separated.
Improvement - Timeline section is added into documentation.
Improvement - State slug field is set as slug version of its label if it is not given on saving.

django-river - 0.7.0

Published by javrasya about 8 years ago

Improvement - Python version 3.5 support is added. (not for Django1.7)
Improvement - Django version 1.9 support is added. (not for Python3.3 and PyPy3)

django-river - 0.8.0

Published by javrasya about 8 years ago

Deprecation - ProceedingTrack is removed. ProceedingTracks were being used to keep any transaction track to handle even circular one. This was a workaround. So, it can be handled with Proceeding now by cloning them if there is circle. ProceedingTracks was just causing confusion. To fix this, ProceedingTrack model and its functions are removed from django-river.
Improvement - Circular scenario test is added.
Improvement - Admins of the workflow components such as State, Transition and ProceedingMeta are registered automatically now. Issue #14 is fixed.

django-river - 0.8.1

Published by javrasya about 8 years ago

Bug - ProceedingMeta form was causing a problem on migrations. Accessing content type before migrations was the problem. This is fixed by defining choices in init function instead of in field

django-river - 0.8.2

Published by javrasya about 8 years ago

Bug - Features providing multiple state field in a model was causing a problem. When there are multiple state field, injected attributes in model class are owerriten. This feature is also unpractical. So, it is dropped to fix the bug.
Improvement - Initial video tutorial which is Simple jira example is added into the documentations. Also repository link of fakejira project which is created in the video tutorial is added into the docs.
Improvement - No proceeding meta parent input is required by user. It is set automatically by django-river now. The field is removed from ProceedingMeta admin interface too.
Improvement - django1.10 support is added.