IQSS / IQSS/dataverse-frontend
Define Dataverse Frontend CHANGELOG strategy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
We currently do not have a CHANGELOG for the Dataverse Frontend repository. We should define a process to create and maintain one, so that all changes are clearly documented and easy to review.
What kind of user is the feature intended for?
Community
What inspired the request?
Sprint planning discussion
What existing behavior do you want changed?
N/A
Any brand-new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
None
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 no files, tests, or entry points. Start by reviewing the repository’s current release and documentation practices; done means an agreed, documented process for creating and maintaining the Dataverse Frontend CHANGELOG.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100