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

Relevant Issues and Features - From RAVEN v1.1 to v2.0 #988

Closed
10 tasks done
alfoa opened this issue May 10, 2019 · 1 comment
Closed
10 tasks done

Relevant Issues and Features - From RAVEN v1.1 to v2.0 #988

alfoa opened this issue May 10, 2019 · 1 comment
Labels
devel issues in current devel priority_normal RAVENv2.0 Defects and Features in release of RAVEN v2.0 task This tag should be used for any new capability, improvement or enanchment under-discussion issues that are under discussion

Comments

@alfoa
Copy link
Collaborator

alfoa commented May 10, 2019


Issue Description

This issue is a floating tracking system for recording all the main defects and features addressed from a release to the other.
Base Release: RAVEN v.1.1
Next Release: RAVEN v.2.0

Addressed Defects:

New Features:


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?
@alfoa alfoa added devel issues in current devel priority_normal task This tag should be used for any new capability, improvement or enanchment under-discussion issues that are under discussion labels May 10, 2019
@alfoa alfoa added the RAVENv2.0 Defects and Features in release of RAVEN v2.0 label Jun 25, 2019
@alfoa alfoa mentioned this issue Jun 25, 2019
10 tasks
@alfoa
Copy link
Collaborator Author

alfoa commented Apr 27, 2020

RAVEN V.2.0 has been released.

This issue can be closed, and another one containing the reference of tasks/defects from RAVEN v.2.0 to RAVEN v.2.1 has been opened:

#1225

@alfoa alfoa closed this as completed Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devel issues in current devel priority_normal RAVENv2.0 Defects and Features in release of RAVEN v2.0 task This tag should be used for any new capability, improvement or enanchment under-discussion issues that are under discussion
Projects
None yet
Development

No branches or pull requests

1 participant