New version: TheDocumentFoundation.LibreOffice.LTS version 7.6.4

[CoolPlayLin]

• Resolves [Update Request]: LibreOffice.LTS 7.6.4 #138471

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Hi @CoolPlayLin,

This PR's version number 7.6.4 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 7.5.9.2, which has 4 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)

(Automated response - build 720)

[Mat2095]

Hm, could this lead to issues, if two packages (TheDocumentFoundation.LibreOffice and TheDocumentFoundation.LibreOffice.LTS) both have the same version of the same application, meaning identical installer, product-code and so on? At the moment there is no overlap in versions yet.

[stephengillie]

Hi @Trenly and @mdanish-kh,

What are your thoughts on having duplicate installer details in 2 different PackageIdentifiers, as described by @Mat2095?

[mdanish-kh]

After committing the suggested changes, you would also have to rename the version folder to match the new PackageVersion. The folder under manifests/t/TheDocumentFoundation/LibreOffice/LTS should be renamed from 7.6.4 -> 7.6.4.1

A quick and easy way to do this would be here in GitHub Web by pressing the . (dot) key on your keyboard that'll open up the PR in VS Code Online. Navigate to Explorer menu, find the required folder and make the appropriate rename changes.

After that, stage and commit your changes from Source Control menu on the left. (The changes are automatically pushed)

[mdanish-kh]

Suggested change

	PackageVersion: 7.6.4
	PackageVersion: 7.6.4.1

[mdanish-kh]

Suggested change

	PackageVersion: 7.6.4
	PackageVersion: 7.6.4.1

[mdanish-kh]

Suggested change

	PackageVersion: 7.6.4
	PackageVersion: 7.6.4.1

[mdanish-kh]

Hi @ Trenly and @ mdanish-kh,

What are your thoughts on having duplicate installer details in 2 different PackageIdentifiers, as described by @ Mat2095?

If I'm understanding this correctly - 7.6.4.1 has recently become an LTS version? If that is the case, we can consider removing it first from TheDocumentFoundation.LibreOffice package id, and then merge in this PR.

[Mat2095]

If I'm understanding this correctly - 7.6.4.1 has recently become an LTS version? If that is the case, we can consider removing it first from TheDocumentFoundation.LibreOffice package id, and then merge in this PR.

Yes, 7.6.4.1 is the current LTS version (since ~2 weeks).
Could removing this version from TheDocumentFoundation.LibreOffice lead to an issue like the following?

• user installed TheDocumentFoundation.LibreOffice 7.6.4.1 in the past
• it gets removed and added to TheDocumentFoundation.LibreOffice.LTS
• user searches for updates and now receives updates from TheDocumentFoundation.LibreOffice.LTS instead of TheDocumentFoundation.LibreOffice

[mdanish-kh]

Yes, 7.6.4.1 is the current LTS version (since ~2 weeks). Could removing this version from TheDocumentFoundation.LibreOffice lead to an issue like the following?

* user installed `TheDocumentFoundation.LibreOffice` `7.6.4.1` in the past

* it gets removed and added to `TheDocumentFoundation.LibreOffice.LTS`

* user searches for updates and now receives updates from `TheDocumentFoundation.LibreOffice.LTS` instead of `TheDocumentFoundation.LibreOffice`

Ah yes, I believe that is going to be a side-effect of this change. Not sure what's more valuable - keeping existing users to get releases from the same "channel" they installed from, or correctly reflecting the status of each version in the repository. I'm inclining towards the second option, not the most ideal for existing users, but winget list libreoffice will help them see that they're now on the LTS version. cc @Trenly thoughts?

I think the actual solution would be implementation of proper channel support in winget:

• Support different release channels [released, beta, alpha] winget-cli#147

[microsoft-github-policy-service]

Hello @CoolPlayLin,

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any recent activity. It will be closed if no further activity occurs within 3 days of this comment.

Template: msftbot/noRecentActivity

[Mat2095]

@mdanish-kh Well, in the meantime 7.6.5 has been released. That version does not exist (and never existed) for the TheDocumentFoundation.LibreOffice package, so it does not create any issues. So I will close my issue for 7.6.4 LTS and hopefully I can manage to create a PR myself :)