docs: link completion criteria to Gitea issues and add issue tracking guidance
- Created 52 Gitea issues across milestones 1-7, one per completion criterion - Each criterion now links to its corresponding issue ([#N](url) format) - Milestone Tracking sections updated with Issue Updates subsection: when/how to comment, close issues via CLI or web UI - Phases 4-7 criteria converted from plain bullets to checkbox format
This commit is contained in:
@@ -20,6 +20,23 @@ Every module, feature, and test in the porting database must have either a .NET
|
||||
|
||||
This phase corresponds to **Milestone 4** in [Gitea](https://gitea.dohertylan.com/dohertj2/natsnet/milestone/4). When starting this phase, verify the milestone is open. Assign relevant issues to this milestone as work progresses.
|
||||
|
||||
### Issue Updates
|
||||
|
||||
Each completion criterion has a corresponding Gitea issue. Update issues as you work:
|
||||
|
||||
- **Starting a criterion**: Add a comment noting work has begun
|
||||
- **Blocked**: Add a comment describing the blocker
|
||||
- **Complete**: Close the issue with a comment summarizing the result (e.g., counts, verification output)
|
||||
|
||||
Close issues via CLI:
|
||||
```bash
|
||||
curl -s -X PATCH "https://gitea.dohertylan.com/api/v1/repos/dohertj2/natsnet/issues/{N}" \
|
||||
-H "Content-Type: application/json" \
|
||||
-H "Authorization: token $GITEA_TOKEN" \
|
||||
-d '{"state":"closed"}'
|
||||
```
|
||||
Or close via the Gitea web UI.
|
||||
|
||||
## Solution Structure
|
||||
|
||||
Define the .NET solution layout following standard conventions:
|
||||
@@ -184,11 +201,11 @@ dotnet run --project tools/NatsNet.PortTracker -- feature list --status n_a --db
|
||||
|
||||
## Completion Criteria
|
||||
|
||||
- Every module has `dotnet_project` and `dotnet_namespace` set, or status is `n_a` with a reason
|
||||
- Every feature has `dotnet_project`, `dotnet_class`, and `dotnet_method` set, or status is `n_a` with a reason
|
||||
- Every test has `dotnet_project`, `dotnet_class`, and `dotnet_method` set, or status is `n_a` with a reason
|
||||
- Naming follows PascalCase and the namespace hierarchy described above
|
||||
- No two features map to the same class + method combination (collisions)
|
||||
- [ ] [#25](https://gitea.dohertylan.com/dohertj2/natsnet/issues/25) Every module has `dotnet_project` and `dotnet_namespace` set, or status is `n_a` with a reason
|
||||
- [ ] [#26](https://gitea.dohertylan.com/dohertj2/natsnet/issues/26) Every feature has `dotnet_project`, `dotnet_class`, and `dotnet_method` set, or status is `n_a` with a reason
|
||||
- [ ] [#27](https://gitea.dohertylan.com/dohertj2/natsnet/issues/27) Every test has `dotnet_project`, `dotnet_class`, and `dotnet_method` set, or status is `n_a` with a reason
|
||||
- [ ] [#28](https://gitea.dohertylan.com/dohertj2/natsnet/issues/28) Naming follows PascalCase and the namespace hierarchy described above
|
||||
- [ ] [#29](https://gitea.dohertylan.com/dohertj2/natsnet/issues/29) No two features map to the same class + method combination (collisions)
|
||||
- [ ] Close the Phase 4 milestone in Gitea:
|
||||
```bash
|
||||
curl -s -X PATCH "https://gitea.dohertylan.com/api/v1/repos/dohertj2/natsnet/milestones/4" \
|
||||
|
||||
Reference in New Issue
Block a user