Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep iteration in the approvals #110

Closed
javrasya opened this issue Oct 25, 2019 · 0 comments
Closed

Keep iteration in the approvals #110

javrasya opened this issue Oct 25, 2019 · 0 comments
Labels
Milestone

Comments

@javrasya
Copy link
Owner

@javrasya javrasya commented Oct 25, 2019

Description:
Source and destination state information are not enough to keep track of the order since there can be cyclic transitions with django-river. It is good to keep an iteration number which represents the order of the transition in the tree. As cycles happen, this number would also increase.

Acceptance Criteria:

  • Introduce an iteration number in approvals to keep track of orders properly.
javrasya added a commit that referenced this issue Oct 25, 2019
…e order of the transitions properly
javrasya added a commit that referenced this issue Oct 25, 2019
…e order of the transitions properly
javrasya added a commit that referenced this issue Oct 26, 2019
…well and update changelogs
javrasya added a commit that referenced this issue Oct 27, 2019
javrasya added a commit that referenced this issue Oct 27, 2019
javrasya added a commit that referenced this issue Oct 27, 2019
@javrasya javrasya closed this Oct 27, 2019
@javrasya javrasya added this to the 2.1.0 milestone Oct 28, 2019
javrasya added a commit that referenced this issue Nov 17, 2019
javrasya added a commit that referenced this issue Nov 17, 2019
javrasya added a commit that referenced this issue Nov 17, 2019
javrasya added a commit that referenced this issue Nov 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.