You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[various Latin (lowercase-only, case pairs, modifiers)](https://github.com/unicode-org/unicodetools/blob/4f8a581c77fdda2d572a16b28e74d865a689108e/unicodetools/src/main/resources/org/unicode/text/UCD/AdditionComparisons/155.txt#L11-L72),
-[characters decomposing to sequences](https://github.com/unicode-org/unicodetools/blob/5f6bc190766ed9104cebc828f1e193517f4d74ec/unicodetools/src/main/resources/org/unicode/text/UCD/AdditionComparisons/141.txt#L13-L20).
-[ ] Correct properties (often in PropList.txt, but also VerticalOrientation.txt, East_Asian_Width.txt, etc.).
67
+
-[ ] Commit
68
+
-[ ] UCD — [Regenerate](#regenerate-ucd)
69
+
59
70
---
60
71
PR preparation:
61
-
-[ ] If from SAH — Link SAH issue
62
-
-[ ] If from ESC or CJK — Mention ESC or CJK in the PR description
63
-
-[ ] When for a UTC decision — Cite in the format UTC-\d\d\d-[MC]\d+ or with a link.
64
-
-[ ] Link RMG issue
65
-
-[ ] Whenever there is a Proposal document — Cite L2 number in the format L2/yy-nnn
72
+
-[ ] UTC decision — Cite if available
73
+
- Copy from the minutes (this includes a link), or, if unavailable, use the form UTC-\d\d\d-[MC]\d+.
74
+
- If there is no UTC decision but an L2 document is available, cite as L2/\d\d-\d+.
75
+
-[ ] Working group — Mention:
76
+
- Proposals from SAH — Link SAH issue
77
+
- Proposals from ESC or CJK — Mention ESC or CJK in the PR description
78
+
-[ ] RMG issue — Link
66
79
-[ ] data-for-new — Set label
67
-
-[ ] pipeline-* — Set label to **pipeline-recommended-to-UTC** if the characters are not yet in the pipeline, and **pipeline-provisionally-assigned**, or **pipeline-`<version>`** depending on their status in [the Pipeline](https://unicode.org/alloc/Pipeline.html#future).
80
+
-[ ] pipeline-* — Set label:
81
+
-**pipeline-recommended-to-UTC** if the characters are not yet in the pipeline,
82
+
-**pipeline-provisionally-assigned**, or
83
+
-**pipeline-`<version>`** depending on their status in [the Pipeline](https://unicode.org/alloc/Pipeline.html#future).
68
84
-[ ] PR button — Set to DRAFT pull request
69
85
- unless approved for the upcoming version
70
86
-[ ] PR button — Press
@@ -75,7 +91,24 @@ PR preparation:
75
91
in the UCD invariants.
76
92
UCA and security data issues are addressed later in the process,
77
93
before the start of β review.
78
-
94
+
-[ ] PAG review summary for the report — Write
95
+
- For proposals from SAH, use the following template in the SAH issue:
96
+
```markdown
97
+
# PAG Review
98
+
99
+
[Name] drafted the UCD change in https://github.com/unicode-org/unicodetools/pull/[number].
100
+
101
+
## PAG report
102
+
103
+
[Summarize the propertywise tests, omitting the uninteresting, _e.g._, differences in Block or
104
+
Unicode_1_Name, and calling out the nontrivial (in particular, any issues that were caught by
105
+
the tests).]
106
+
```
107
+
- For proposals from CJK, file a PAG issue of type `Document`, citing the proposal.
108
+
Put the review in the `Background information / discussion` section, and link the pull request
109
+
in the `Internal` section. See, _e.g._, https://github.com/unicode-org/properties/issues/366.
110
+
- [ ] PAG dashboard status of SAH or PAG issue — Set to `Review`
111
+
- [ ] Pipeline dashboard PAG status of RMG issue — Set to `data review`
79
112
## Scripts
80
113
81
114
There are a variety of setups for unicodetools, depending on OS, in-source vs. out-of-source, git practices, etc.
0 commit comments