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

Add a shared tag for RC versions #65

Open
nbraud opened this issue Oct 27, 2021 · 3 comments
Open

Add a shared tag for RC versions #65

nbraud opened this issue Oct 27, 2021 · 3 comments
Labels
Request Request for image modification or feature

Comments

@nbraud
Copy link

nbraud commented Oct 27, 2021

The CPython images provide rc and rc-slim tags to refer to whatever is the current development version, in addition to 3 / latest. Would it be possible to have those for PyPy?

@wglambert wglambert added the Request Request for image modification or feature label Oct 27, 2021
nbraud added a commit to ppb/ppb-vector that referenced this issue Oct 27, 2021
Unfortunately, the pypy images do not have an `rc` tag or such:
  docker-library/pypy#65
@tianon
Copy link
Member

tianon commented Nov 5, 2021

It's certainly possible, but it's going to be pretty manual, and I'm not sure I get the benefit? I feel like the concept of "RCs" in Python is a little more well defined than in PyPy, where releases have previously gone from "beta" to "GA" without much warning (because by the time they're released as a beta, they're already pretty stable 😄).

@nbraud
Copy link
Author

nbraud commented Dec 12, 2021

Hi Tianon!

It's certainly possible, but it's going to be pretty manual, and I'm not sure I get the benefit?

My usecase is simply being able to pull the latest development version in CI for downstream projects, and be informed automatically if some change breaks our testsuite. It's pretty helpful in making sure we stay compatible with newer versions of CPython or PyPy without having to scramble right after a new release.

I feel like the concept of "RCs" in Python is a little more well defined than in PyPy, where releases have previously gone from "beta" to "GA" without much warning (because by the time they're released as a beta, they're already pretty stable smile).

I'm not sure I follow, here. There are already various tags (such as 3.8) to select development versions (that are newer than latest), all I'm asking about is a tag that allows selecting the development version (without knowing that it is currently 3.8)

If the concept of an RC version doesn't work for PyPy's development cycle, calling the tag dev or somesuch is fine; I only mentioned rc since it is the equivalent in CPython's images.

@tianon
Copy link
Member

tianon commented Dec 14, 2021

I guess what I'm trying to get at is that https://www.pypy.org/download.html (or even https://www.pypy.org/download_advanced.html) doesn't really differentiate between 3.8, 3.7, or 2.7, even though that 3.8 is considered a "beta" release.

The only place that I'm aware of that really makes it clear that 3.8 is "beta" is the blog post which announced it: https://www.pypy.org/posts/2021/10/pypy-v736-release.html (and my understanding previously has been that it stays beta until it isn't anymore, and that the "beta" status of it thus isn't particularly well-defined, which makes it a bit difficult to track accurately).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Request Request for image modification or feature
Projects
None yet
Development

No branches or pull requests

3 participants