[Documentation] What is the status of Pyston 2.3, and supported/released Pyston versions in general

[biblicabeebli]

There is no obvious documentation of the statuses of various working/supported versions of Pyston.

Pyston version 2.3 is apparently released, but I literally only discovered it because pyenv added a new version entry for pyston. The only obvious reference in the wiki is some benchmarks for Windows vs WSL

The only other public-facing comment on the status of Pyston that I have been able to find is https://blog.pyston.org/, which also lacks this information.

The branch containing pyston release 2.2 is named in shorthand as rel2.2, but there is no structure or existing pattern to the branch names such as release/2.2 or, for development branches, something like feature/some_branch_name.

The github repo should have some obvious documentation, ideally on the front page, e.g. in the readme.md on the primary branch, indicating the recent and currently supported versions, plus any planned dates of major versions going out of support.

[kmod]

Thanks for checking out Pyston! Our releases our posted here; we occasionally announce the releases on other channels, but the most up-to-date info will be on the releases page.

We don't have an official support/deprecation policy, but informally it is something like "we will try to help with past releases, but the only supported one is the most recent one".

[undingen]

I think this setting should at least notify you after we published a new release:

[biblicabeebli]

(Herp Derp, github moved the former releases tab to the side of the page, my bad.)

I think you should make a dedicated wiki page about aspects of support, even if it seems empty or like it is just fluff. I think it is okay to provide a statement on the page that support may have to be provisional to some extent, and that you are looking for input on what policy-level things currently block a potential user to become a real user.

Pyston seems like a no-brainer drop-in upgrade from a tech perspective, but it is also new and untested and business doesn't like risk. Assurances of some basics, "support for consistent identical behavior" (or whatever) with target versions of cPython would help, and a statement on process for how security fixes from upstream cPython are incorporated, would go a long way to "selling" Pyston to a further audience. Yes you've probably mentioned it elsewhere, but I think you also need the SEO.

(My situation is I have a chunk of raw-python code running on bulk data on ubuntu servers. This appears to be your supported configuration, so I hope to have the opportunity to try it out.)