Improve/start versioning
Open
- Dominant language
- XSLT
- Stars
- 136
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
Define 0.2 as a first version and start creating new versions after fixes and improvements.
## Tasks
- [ ] Start using GitHub tags for each version.
- [ ] Start a changelog file with info about CKAN version covered + bugs + fixes
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by reviewing the repository's current version information and GitHub tag history, then define 0.2 as the baseline and establish how later fixes and improvements are tagged. Done means version tags are used and a changelog records the CKAN version covered, bugs, and fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100