JuliaCollections / JuliaCollections/DataStructures.jl
Maturing out the package (Path to DataStructures.jl v1.0)
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 745
- Forks
- 261
- PR merge metrics
- No merged PRs in 30d
Description
What do we need to do before we would be happy to tag DataStructures.jl v1.0?
I mean, we are one of the most common dependencies in the package ecosystem,
and julia 1.0 is out.
My thoughts;
- Search the code base for anything written in outmoded styles (e.g. #472)
- Get rid of anything deprecated #477 (but that will need to be done again after)
- Maybe split up the package #310, but noting that all the packages sliced out that way will want to hit 1.0 before (or at the same time as) DataStructures.jl does.
It hurts people when we break things, and while we are good at deprecating,
getting on the the "strict" side of semver is something we need to do for the sake of the ecosystem
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 DataStructures.jl code base for outmoded styles, using #472 as the named example, and read the context of #477 and #310. The issue is done when the v1.0 requirements are agreed, remaining compatibility work is identified, and the package-splitting question has a decided path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100