Perform Release Review
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, markdown
- Domain
- accessibility, release, testing
Research direction
Start by reviewing the changes in v0.0.7..main, then check tests, lint, naming, docs, the README, and accessibility with axe, the accessibility tree, and a keyboard trace. Reproduce suspicious behavior and record findings with file and line references at the review commit. File prioritized findings as issues by area, keep security findings in .issues/ with a vague line in priorities.md, and revisit dates for following milestones.
Written by the indexing model from the issue text.
Description
The last task in this milestone: a look back over what it changed, before it's tagged.
Review v0.0.7..main for:
- Technical debt: duplication, dead code, things worked around rather than fixed
- Quality: tests missing for what changed, lint, naming, docs and the README
- Correctness: reproduce anything suspicious; file:line as of the review's commit
- Accessibility: axe, the accessibility tree and a keyboard trace of what's new (WCAG 2.2 AA)
Then:
- File each finding as an issue (or a checklist in one issue per area), prioritized into an upcoming milestone; open a new milestone if none fits
- Keep security findings out of GitHub: they go in
.issues/, with a vague line in priorities.md - Write up a report: each finding, the milestone it went to and why, and what looked like a finding but was set aside, and why
- Revisit the dates of the milestones that follow; if we're ahead, pull work or polishes forward
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OWASP/CheatSheetSeries#3018 ·
Maintainers usually reply within 1 day
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
GoogleChrome/modern-web-guidance-src#3675 · 2 comments ·
Maintainers usually reply within 1 day