Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make 3.x match 3.x-dev in case there is no stable release yet #501

Closed
lazka opened this issue Sep 20, 2022 · 4 comments · Fixed by #414
Closed

Make 3.x match 3.x-dev in case there is no stable release yet #501

lazka opened this issue Sep 20, 2022 · 4 comments · Fixed by #414
Labels
feature request New feature or request to improve the current logic

Comments

@lazka
Copy link

lazka commented Sep 20, 2022

Current situation: We will get 3.11 in about a month and I want to test it to CI from now on.

This means I now have to use 3.11-dev and in one month downgrade to 3.11 to get the stable release from then on.

Ideally 3.11 would match 3.11-dev as long as there exists no stable release yet for that version, unless I'm missing something.

I know it's possible to do 3.11.0-alpha - 3.11.0 but that still would require me to clean things up eventually and I'd like to add it once and never touch it again.

@lazka lazka added feature request New feature or request to improve the current logic needs triage labels Sep 20, 2022
@lazka lazka changed the title Make 3.X match dev versions in case there is no stable release yet Make 3.x match 3.x-dev versions in case there is no stable release yet Sep 20, 2022
@lazka lazka changed the title Make 3.x match 3.x-dev versions in case there is no stable release yet Make 3.x match 3.x-dev in case there is no stable release yet Sep 20, 2022
@EwoutH
Copy link

EwoutH commented Sep 20, 2022

Yes, this would be a great feature. I support this!

@vsafonkin
Copy link

Hi @lazka, thank you for your help, we will take a look at this.

@mayeut
Copy link
Contributor

mayeut commented Oct 1, 2022

This is #414

@brcrista
Copy link
Contributor

brcrista commented Oct 4, 2022

Let's consolidate on #213 since that's been around for a while and has more people following it.

@brcrista brcrista closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants