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.

Sign up for GitHub

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

Jump to bottom

[TASK] User Guide #37

Open
5 of 10 tasks
worseliz opened this issue Oct 25, 2021 · 0 comments
Open
5 of 10 tasks

[TASK] User Guide #37

worseliz opened this issue Oct 25, 2021 · 0 comments
Assignees
@worseliz
Labels
priority-normal task New feature or request

Comments

@worseliz
Copy link
Collaborator

worseliz commented Oct 25, 2021 •
edited
Loading

Issue Description

Create a user guide for TEAL to help new users learn TEAL on their own. Also include copy-paste examples from real TEAL applications.

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?
@worseliz worseliz added the task New feature or request label Oct 25, 2021
@worseliz worseliz self-assigned this Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@worseliz worseliz

Labels
priority-normal task New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@worseliz