Releases: javrasya/django-river
2.0.0
- Improvement - [ #90,#36 ]: Finding available approvals has been speeded up ~x400 times at scale
- Improvement - #92: It is mandatory to provide initial state by the system user to avoid confusion and possible mistakes
- Improvement - #93 : Tests are revisited, separated, simplified and easy to maintain right now
- Improvement - #94 : Support class level hooking. Meaning that, a hook can be registered for all the objects through the class api
- Bug - #91 : Callbacks get removed when the related workflow object is deleted
- Improvement - Whole
django-river
source code is revisited and simplified - Improvement - Support
Django v2.2
- Deprecation -
Django v1.7
,v1.8
,v1.9
andv1.10
supports have been dropped
1.0.2
1.0.1
1.0.0
django-river
is finally having it's first major version bump. In this version, all code and the APIs are revisited
and are much easier to understand how it works and much easier to use it now. In some places even more performant.
There are also more documentation with this version. Stay tuned :-)
- Support
Django2.1
- Support multiple state fields in a model
- Make the API very easy and useful by accessing everyhing via model objects and model classes
- Simplify the concepts
- Migrate ProceedingMeta and Transition into TransitionApprovalMeta for simplification
- Rename Proceeding as TransitionApproval
- Document transition and on-complete hooks
- Document transition and on-complete hooks
- Imrove documents in general
- Minor improvements on admin pages
- Some performance improvements
0.10.0
- Improvement - Django has dropped support for pypy-3. So, It should be dropped from django itself too.
- Remove -
pypy
support has been dropped - Remove -
Python3.3
support has been dropped - Improvement -
Django2.0
support withPython3.5
andPython3.6
is provided
0.9.0
#30 -Bug - Missing migration file which is 0007 because of Python2.7 can not detect it.
#31 - Improvement - unicode issue for Python3. (Thanks to @psychok7 )
#33 - Bug - Automatically injecting workflow manager was causing the models not have default objects one. So, automatic injection support has been dropped. If anyone want to use it, it can be used explicitly.
#35 - Bug - This is huge change in django-river. Multiple state field each model support is dropped completely and so many APIs have been changed. Check documentations and apply changes.
0.8.2
- 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.
0.8.1
0.8.0
- 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.