OpenFreeEnergy / OpenFreeEnergy/openfe-benchmarks
[proposal] Agree on release strategy
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 2
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 8
Description
It's important for us to work out what releases mean when it comes to input data.
The current suggestion is:
- Adding new datasets is a minor release.
- Altering existing datasets is a major release.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are mentioned. Start by reviewing how input datasets and releases are currently handled, then seek agreement on whether adding datasets is a minor release and altering existing datasets is a major release.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100