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

Version status matrix for TYPO3, PHP ...? #144

Open
sypets opened this issue Apr 18, 2020 · 3 comments
Open

Version status matrix for TYPO3, PHP ...? #144

sypets opened this issue Apr 18, 2020 · 3 comments
Assignees

Comments

@sypets
Copy link

sypets commented Apr 18, 2020

I would love to see an overview, a matrix what is currently supported, in which state it is in and what are the requirements.

While I really like the layout and design of get.typo3.org (it is very appealing visually), a very terse table (where you have the most important information on one page and don't have to click) might be helpful.

For example,

  • You have to click if you want to find the PHP support for ELTS versions
  • If you want to find the PHP support of older versions (before ELTS) ...

Examples:

  1. TYPO3 release / PHP / MySQL version matrix

versions
Taken from Stack Overflow answer: https://stackoverflow.com/a/12911016/2444812, unfortunately no longer maintained for 8,9 and 10.

BTW, this is the answer with the highest number of upvotes on Stack Overflow, I sometimes look at the highest voted questions or answers to see what people find useful and what may be missing in the documentation.

  1. PHP Unsupported branches: https://www.php.net/eol.php

phpeol

@bmack
Copy link
Member

bmack commented Apr 18, 2020

We have an extension / plugin on typo3.org for that in place already:

https://typo3.org/cms/roadmap

One of the reasons why we put things on get.typo3.org is to get rid of the typo3.org/download page and various other locations, just to centralize where to download TYPO3.

The release dates are really something to maintain twice currently (support times), but I have to be honest - I would much rather have a CMS with an extension to manage this content than with API endpoints on get.typo3.org - but having this shown in two places with one UI for managing this content would be great.

@gilbertsoft
Copy link
Collaborator

So we should work into this direction and use the get.t3o api in the cms extension, I guess this will solve the most things. Will have a look at this extension and come back...

@gilbertsoft gilbertsoft self-assigned this Apr 20, 2020
@gilbertsoft
Copy link
Collaborator

#385 should partially solve this issue

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

No branches or pull requests

3 participants