NYCPlanning / NYCPlanning/data-engineering
PLUTO Versioning Strategy Bug
Open
Nobody has claimed this yet.
db-pluto
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
PLUTO version isn't determined correctly between years. For example, it currently determines 24v5 as the next version for 24v4.1; expected next version is 25v1.
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
Locate the PLUTO version-determination logic and reproduce the transition from 24v4.1. Verify that a version in the final year rolls forward to 25v1 rather than 24v5. Done means the reported boundary case and related versioning behavior produce the expected next version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100