Question: what the format of version number will be for LTS in the future?

[kirk0830]

Details

The interface with ASE (abacuslite) always parses the output of ABACUS. Because there are mainly two different formats of running log (the LTS/<3.10 and the 3.9.0.x/3.11) presently, the abacuslite will always consult the version of ABACUS by running command abacus --version, and parse the version number to select a proper output reader.
However, as LTS and develop are two living branches and will continuously have new releases, abacuslite needs a robust strategy to be always capable in distinguishing between them two by the version number.
So I want to know how the version number of LTS branch will vary in the future? Will it always be 3.10.x? If one day the version number of LTS switches to 3.11.x, will the output format be identical with the develop branch?
Thanks.

Have you read FAQ on the online manual http://abacus.deepmodeling.com/en/latest/community/faq.html

• Yes, I have read the FAQ part on online manual.

Task list for Issue attackers (only for developers)

• Understand the problem or question described by the user.
• Check if the issue is a known problem or has been addressed in the documentation.
• Test the issue or problem on a similar system or environment, if possible.
• Identify the root cause or provide clarification on the user's question.
• Provide a step-by-step guide, including any necessary resources, to resolve the issue or answer the question.
• If the issue is related to documentation, update the documentation to prevent future confusion (optional).
• If the issue is related to code, consider implementing a fix or improvement (optional).
• Review and incorporate any relevant feedback from users or developers.
• Ensure the user's issue is resolved or their question is answered and close the ticket.

[mohanchen]

The 3.10 LTS version will be replaced by a new LTS release in the near future, which is expected to be the 3.11 LTS version (I guess).

Regarding your question about future version numbering and output format consistency:
The LTS branch will continue remain for a while, but not remain at 3.10.x permanently. As mentioned, it will be upgraded to 3.11.x as the next LTS release.

When the LTS branch moves to 3.11.x, its output log format will be consistent with the 3.11 development branch, so abacuslite will be able to use the same output reader for both the LTS and develop versions starting from 3.11.

Going forward, the LTS branch will follow a similar model: each new LTS release will align its version number and output format with the corresponding stable develop version, ensuring a unified parsing strategy for abacuslite.

This design ensures that abacuslite can reliably distinguish branches by version number and maintain robust compatibility as both LTS and develop branches continue to evolve.

[kirk0830]

The 3.10 LTS version will be replaced by a new LTS release in the near future, which is expected to be the 3.11 LTS version (I guess).

Regarding your question about future version numbering and output format consistency: The LTS branch will continue remain for a while, but not remain at 3.10.x permanently. As mentioned, it will be upgraded to 3.11.x as the next LTS release.

When the LTS branch moves to 3.11.x, its output log format will be consistent with the 3.11 development branch, so abacuslite will be able to use the same output reader for both the LTS and develop versions starting from 3.11.

Going forward, the LTS branch will follow a similar model: each new LTS release will align its version number and output format with the corresponding stable develop version, ensuring a unified parsing strategy for abacuslite.

This design ensures that abacuslite can reliably distinguish branches by version number and maintain robust compatibility as both LTS and develop branches continue to evolve.

@mohanchen thanks, I will update the abacuslite soon accordingly