Rules version 3.5 release
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- release
Research direction
Review the saved release draft and compare its contents with the repository's individual .catz, .bsi, and other data files. Start by determining how releases are packaged; done when the rules 3.5 release includes all intended artifacts, not only the source-code ZIPs.
Written by the indexing model from the issue text.
Description
@KurganFr Everything is updated to rules 3.5, so I'd say this repo is ready for a release. Any chance you could do that?
I tried making a release on my fork, but it only contained the "source code" zips, and not all the individual .catz files. And certainly not the .bsi files and other stuff I have no idea where they're from. Anyway, I saved a release draft.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
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.
More from BSData/deadzone
-
2020 data update. Open
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100