[xlnt] update to 1.6.0

[m7913d]

Library name

xlnt

New version number

1.6.0

Other information that may be useful (release notes, etc...)

As discussed in issue tfussell/xlnt#748, the main repo of xlnt has been unmaintained for several years.
In order to continue this great project started by tfussell, the xlnt community has created a new repo to support further development by the community.

We are planning to release a new version (1.6.0) soon, mostly containing bug fixes and support for the latest toolchains. The changes are source-code backwards compatible with the 1.5.0 xlnt release of tfussell.
I'm already posting this issue now, to be able to take your feedback into account, before actually releasing the new xlnt version:

• Would you accept a repo switch from tfussell to xlnt-community, as the original repo is unmaintained? Advantage of reusing the xlnt port in vcpkg, is that all vcpkg users automatically gets the updated version.
• Or should we create a new port?

[m7913d]

@MonicaLiu0311 Any update on how we should proceed to update the xlnt package in vcpkg? Or wouldn't you accept a new version from a cloned repo, even if the original repo is unmaintained?

[MonicaLiu0311]

Sorry to keep you waiting, the team is in discussion.

[github-actions]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[m7913d]

Just posting a comment to avoid automatic closure. We are still waiting for the team's decision.

[wuxianggujun]

Sorry to keep you waiting, the team is in discussion.抱歉让您久等了，团队正在讨论中。

When will xlnt community edition be added to vcpkg

[ianalexis]

UP

[m7913d]

@MonicaLiu0311 Do you have any idea when the team will make a decision?

[MonicaLiu0311]

@BillyONeal @vicroms

[icyfox168168]

希望通过