Specification release automation
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
We have currently opted to release published versions of the specifications to https://solidproject.org/TR/ and Editor's drafts to https://solidproject.org/ED/ and while this is something we want to do going forward, automation rather than copying directory structures is preferable.
This issue is to have a placeholder for that.
Contributor 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.
Research direction
The issue names the published-specification path https://solidproject.org/TR/ and Editor's-draft path https://solidproject.org/ED/, but no files, tests, or entry point. Start by locating the current directory-copying process; done means those releases are automated rather than copied manually.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100