-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Remove TheDocumentFoundation.LibreOffice.LTS #162187
Comments
Starting removal |
@vikingnope I think you've mentioned the wrong PR here :D |
oh yep sorry, removed it now |
@SpecterShell, should I remove the SDK LTS as well? |
By deleting the ID "TheDocumentFoundation.LibreOffice.LTS" systems of users who use The currently used download link for 24.2.4.2 is wrong. |
LTS is no longer supported by LibeOffice and this is why it has been removed. I will check out ythe current download link for 24.2.4.2. |
I think there might be an outage with their CDN, there is also a new update 24.2.5.1 so I will add that EDIT: It seems to be going online and offline currently |
Dear all, Until now LibreOffice was calling the versions Stable and Fresh on their website. I think to have a stable (or LTS) ID would nevertheless make sense. At times like now the latest (fresh) and stable (LTS) would be the same version. In one month when 24.8 will be released the LTS will stay on 24.2 and 24.8 would be there additionally. What do you think? |
That version is actually 24.2.5.2 not 24.2.5.1. I'm fixing it. |
It is somehow similar to NodeJS, which has a current (non-LTS) channel and active (LTS) channel, and a major version (e.g., 22.x) in the current channel may go to the active channel when the current channel is moving to the next major version (e.g., 23.x). |
Description of the new feature/enhancement
I'm thinking about removing the
TheDocumentFoundation.LibreOffice.LTS
package and only keeping the non-LTS one, as the LTS one no longer makes sense:Also see: chocolatey-community/chocolatey-packages#2496
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: