maliput and maliput_py versions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 2
Description
### Summary
- `maliput` is [current version 1.1.1](https://github.com/maliput/maliput/blob/main/package.xml#L5C4-L5C4)
- `maliput_py` is [current version 0.1.6](https://github.com/maliput/maliput_py/blob/main/package.xml#L5C4-L5C4)
Both packages have different versions and while working in a colcon ecosystem it makes sense.
### Issue
As tests were recently run for distributing this over pypi it will cause an issue depending on how the wheel is created for distribution.
When creating a wheel of maliput out of maliput_py bindings the version that is used for distribution is the one in maliput_py.
### Proposal
Matching versions between maliput and maliput_py could be the ease path to solve any issue in the future.
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
Compare the version declarations in maliput/package.xml and maliput_py/package.xml, then inspect how the maliput_py bindings are packaged into a PyPI wheel. Check the existing distribution tests or wheel-creation process first; done means the two package versions are aligned and the resulting wheel uses the intended version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100