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

General LOGOS Maintenance Updates #46

Open
10 tasks done
wangcj05 opened this issue Oct 20, 2022 · 0 comments
Open
10 tasks done

General LOGOS Maintenance Updates #46

wangcj05 opened this issue Oct 20, 2022 · 0 comments
Labels
bug Something isn't working priority critical

Comments

@wangcj05
Copy link
Collaborator

wangcj05 commented Oct 20, 2022

Describe the bug

This issue can be used in reference to PRs that only make minor, non-functional changes to LOGOS's code. The expectation would be that these changes are small, do not affect any developer or user functionality, and are independent of other PRs.

A few examples of changes that would apply to this issue:

  • Fixing SyntaxWarnings emitted during runtime
  • Fixing deprecation warnings from dependent library APIs
  • Modifying a comment
  • Raising/lowering the level of output to stdout (debug, warning, all, message, etc)
  • Removing commented code
  • Removing inconsequential code

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context


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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority critical
Projects
None yet
Development

No branches or pull requests

1 participant