Best way to handle `-latest` sufix
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
- Plone CLI version: 1.1
- Python version: 2.7.16
- Operating System: Ubuntu 18.04
Description
I'm having dependency hell when trying to use version 4.3 in plonecli. After trial and error, I've seen that, when prompted to add a version, 4.3-latest is functional. Doing this I've received only a six dependency problem, which I hope will be adressed in https://github.com/plone/Products.CMFPlone/issues/2867.
I was expecting that, setting 4.3 with no patch (MAJOR.MINOR.PATCH) specification, it would get the last stable version in 4.3.x, but it's not the case.
The discussion here is: brainstorm if adding the -latest sufix is a correct assumption and implement it, or add somehow this in the documentation.
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 version prompt behavior in plonecli with 4.3 and 4.3-latest, then trace how version requirements are resolved. Decide whether 4.3 should select the latest stable 4.3.x release or whether -latest should be documented. Done means the chosen behavior is implemented or clearly documented, with the dependency outcome verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100