scikit-learn / scikit-learn/scikit-learn-release
Create a release branch in the scikit-learn-release repo matching the name of the scikit-learn repo
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 4
- Avg merge
- 7h 51m
- Merged PRs (30d)
- 5
Description
I guess we should follow numpy https://github.com/numpy/numpy-release#branches-and-tags.
For NumPy releases, the branch naming should match those of the main numpy/numpy repository, e.g., maintenance/2.3.x for the 2.3.x releases.
See for example https://github.com/numpy/numpy-release/tree/maintenance/2.4.x
We didn't do this for the 1.9.1 because we didn't know ...
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
Start by reviewing the NumPy release branching guidance linked in the issue and compare it with the branch names in the scikit-learn repository. Create the corresponding release branch in scikit-learn-release, matching the scikit-learn naming convention. Done means the expected branch exists and follows the main repository's release name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100