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

[TASK] OutStream Plugin Compatibility #1534

Closed
10 tasks done
PaulTalbot-INL opened this issue Apr 29, 2021 · 1 comment · Fixed by #1535
Closed
10 tasks done

[TASK] OutStream Plugin Compatibility #1534

PaulTalbot-INL opened this issue Apr 29, 2021 · 1 comment · Fixed by #1535
Assignees
Labels
priority_critical RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 task This tag should be used for any new capability, improvement or enanchment

Comments

@PaulTalbot-INL
Copy link
Collaborator

PaulTalbot-INL commented Apr 29, 2021


Issue Description

As a first-of-a-kind, the OutStreams are a good candidate for demonstration with the generic plugin mechanics with lazy plugin loading, separate from the ExternalModels approach (ExternalModel yet needs to be converted to Entity/Interface).


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL PaulTalbot-INL added priority_critical task This tag should be used for any new capability, improvement or enanchment labels Apr 29, 2021
@PaulTalbot-INL PaulTalbot-INL self-assigned this Apr 29, 2021
@PaulTalbot-INL PaulTalbot-INL mentioned this issue Apr 29, 2021
9 tasks
@wangcj05
Copy link
Collaborator

checklist is satisfied.

@wangcj05 wangcj05 added the RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 label Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_critical RAVENv2.1 All tasks and defects that will go in RAVEN v2.1 task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants