Transifex team,
is the tx cli tool still under active development?
The last change added was September 2024 and the release is stuck since then.
There are open PRs and issues that need fixing, but no response on both.
Libraries are heavily outdated such as go (go is at 1.16, we now have 1.25)
This situation does not bring confidence to Transifex.
Any clarifying words?
Martin
Thank you dear mmattel for reaching out and being so candid about your concerns regarding the tx CLI tool. We sincerely appreciate your patience and the detail you’ve provided here.
We want to clarify that the tx CLI is still an actively supported tool within the Transifex ecosystem. Following your feedback, we have escalated this internally to our engineering team for review.
We appreciate you taking the time and bring this forward.
@chrisb
I have now 5 issues open on github/transifex/cli and the last PR action from Transifex, based on my first post, was weeks ago. It looks that developers refused to continue what they have started and confidence continues to go down despite your statement of active development. Such a statement has in my opinion a different outcome that is measurable in merged fixes and provided tool releases. Just my 2c.
Hi @mmattel
We appreciate your comments and interest in improving Transifex CLI, I forward your valuable insights to our team so they can take a look. Rest assured that this will be taken into consideration. As soon as we have any news we’ll make sure to get back to you.
Best regards,
Carlos from Transifex Support
Hello @mmattel
Thank you for taking the time to share this feedback.
I am Panagiotis, the team leader of the Customer Success Engineers at Transifex, by XTM.
The Transifex CLI is designed primarily as a thin wrapper around the Transifex API. Because of that, most new capabilities are typically introduced at the API level first, and the CLI mainly exposes the existing API functionality rather than evolving as a standalone product with many independent features.
That said, the repository is still actively maintained. Our developers have recently resumed reviewing open issues and pull requests, working through them, and closing items where appropriate. I should also mention that work on the CLI is prioritized based on the product’s overall roadmap.
We absolutely appreciate the effort you and others put into opening issues and contributing PRs. They are valuable and help us improve the tooling around the API. Please feel free to continue sharing feedback. It does not go unnoticed, even if responses sometimes take longer than expected.
Thanks again for your patience and for contributing to the project.