Dates on gems—make this make sense
Open
Nobody has claimed this yet.
RubyGems
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
10009 $ gem spec --ruby --remote minitest -v 5.0.0 | rg date
s.date = "2013-05-10"
10010 $ gem spec --ruby --remote minitest -v 6.0.0 | rg date
s.date = "1980-01-02"
How does this make any sense?
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
Reproduce the discrepancy with gem spec --ruby --remote minitest -v 5.0.0 and -v 6.0.0, filtering for date as shown. Trace how the remote gem specifications obtain their dates and establish whether the differing values are expected or should be corrected; done means the behavior is explained and any agreed date handling is covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100