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

Rules Versioning #20

Open
Clayton7510 opened this issue Feb 27, 2017 · 1 comment
Open

Rules Versioning #20

Clayton7510 opened this issue Feb 27, 2017 · 1 comment

Comments

@Clayton7510
Copy link
Collaborator

Rules should be able to be versioned independently of the application code. When a new version of rules is published, the application should load the newly published rules and start running the new rules version in place of the old one.

A couple of things to consider:

  • in-flight rules should not break during a rules version update
  • version updates should have various modes of scheduling (it could use quartz or EJB timer, perhaps)

Initially, repositories for rules could be Maven. Maybe later, Git could be supported.

@Clayton7510
Copy link
Collaborator Author

Starting off, rules can be maintained in Maven as stated above. However, that doesn't really provide a nice mechanism for storing human readable rules, which are addressed in a separate issue. But for this issue, it will do.

@Clayton7510 Clayton7510 self-assigned this Mar 6, 2017
@Clayton7510 Clayton7510 modified the milestones: Release 0.4, Release 0.6 Mar 15, 2017
@Clayton7510 Clayton7510 modified the milestone: Release 0.6 Apr 10, 2017
@Clayton7510 Clayton7510 removed their assignment May 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant