Why are there no new versions anymore ? #3213
-
|
Version 118 is now over a year old, while until that version, every 2-3 months a new version was released. So why is there no new release ? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 19 replies
-
|
Because all work for app now is done by one person: @agnostic-apollo. Some changes incomplete, some not pushed. Termux doesn't hire anyone to work on repositories, people work on it when want to do so and have time. Be patient or use latest git version. To have frequent updates, the application part needs skilled maintainers. For now only package part has enough of them. Btw, the readme document already states this:
|
Beta Was this translation helpful? Give feedback.
-
|
you can get new build from https://github.com/termux/termux-app/actions/workflows/debug_build.yml |
Beta Was this translation helpful? Give feedback.
-
|
For anyone having issues installing these builds, try uninstalling all Termux plugins first (e.g. Termux:API, Termux:Boot and Termux:Widget) |
Beta Was this translation helpful? Give feedback.
-
|
@agnostic-apollo if the current versions in master for Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
why don't you not just install the github builds? These are more recent than anything else in the world :-) If that is important to you... |
Beta Was this translation helpful? Give feedback.
-
|
It's not about that. If it's not stable don't release it. I'm not trying to rush anything. But keeping changes local doesn't help anyone. Making them available helps other contributors, specially when these local changes are mentioned in several pull requests, saying that the changes in the pull request will have to wait for some unpublished changes.... |
Beta Was this translation helpful? Give feedback.
-
|
Drastic changes to the code often needs to be restructured, like split on commits and so. Many changes could be experimental or not finished, the final implementation can be significantly different or be removed at all in the final variant. Lots of commit->revert->rebase->force-push cycles won't help contributors as they may need to do unnecessary work by adapting their code for each pushed changes. Better to wait final changes at the |
Beta Was this translation helpful? Give feedback.
-
In addition to what @sylirre said, I am not keeping changes local for the lulz. If I could have pushed the changes, I would have. However, many, if not most changes are interdependent due to rewrite/refactor of core parts of termux. I can either push all of them together or nothing, since currently committed code will likely not build and even if it did, things may be broken due to other changes that are not committed yet. Fixups to my own changes is also being continuously done too while issues present themselves, and I have however committed most of the stuff now and not much is left on the to-do list before I push changes. |
Beta Was this translation helpful? Give feedback.
-
|
I was not suggesting you should push them to master, only to make them visible in a public branch. And I do appreciate your work. |
Beta Was this translation helpful? Give feedback.
-
|
@sylirre fornwall recently done some changes in his repo. so he is active?. Why he not active in termux development?. Im just curious 😁 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that is known that his account is active on GitHub. We also had few answers from him in one of our issues after long time of silence. But so far there is no interest shown in further participation in Termux development. In age of 40+ people usually have more important tasks to do than play with terminal app on their Android device or spending hours on bumping package versions. |
Beta Was this translation helpful? Give feedback.
-
|
Age is still not an excuse to not transfer or give access to infrastructure accounts to active devs. There is obviously no obligation for him to be active in termux development or support, but there would be or should be for giving others access at least. |
Beta Was this translation helpful? Give feedback.
-
|
I know this is marked as closed and the lack of developers is sad and complicated. |
Beta Was this translation helpful? Give feedback.
-
|
Im also using action builds of these apps👍🏻 |
Beta Was this translation helpful? Give feedback.
-
|
Automatic publishing by GitHub Actions is done already. However per-commit builds won't be published. They are not releases of any kind, even not pre-releases. The current |
Beta Was this translation helpful? Give feedback.
-
|
I see, I am sorry, it was my misunderstanding about the state of the master branch in Termux's development. Thanks for clarifying. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is a bit of a chicken and an egg situation. Personally, I would refrain from investing a lot of time into a project, that cant do a regular release within a long time. Particulary, when the project has not only hundreds of commits in the master branch, but even a couple of larger branches besides this, who are not merged yet. I personally value my own time, and this is simply not a good, sustainable release mechanism, and it will distract further contributors. Just looking at the "last updated" field in F-Droid, lets me think the app is probably dead, and I will not even download it as an user, not to say anything about contributing. Release early, release often, is a well established common practice for good reason. It allows for a much better feedback cycle, better reception from the community, and a more dynamic development overall. But each their own. 🙂 |
Beta Was this translation helpful? Give feedback.
-
You may want to read #3213 (reply in thread) Changes is
Lot of big projects release stable updates after years of work, it obviously does not mean project is somehow dead. Check debian for example (similar goal to us), their stable updates happen every two years. Obviously, they are a much bigger project, but release time point still stands. If someone is thinking such projects are dead, they need to think again and check activities on repos and community channels instead. Moreover, last 10 releases happened within a few months, this is a major refactor of all the core parts, hence is taking this long, next major update will also take a lot of time due to refactoring required for
No, releasing before things have been made final and standardized is a bad way to do stable releases, since if you are continuously breaking stuff, its bad for both users and maintainers. Maintainers are also the ones who would have to deal with all the issues reported by users when their things break, not the users who are in their update-fast craze. Not to mention this update-fast craze in today's world is a major reason for all the bugs and security issues (that everyone then complains about), writing safe, good and stable (non-breaking) code takes time. |
Beta Was this translation helpful? Give feedback.
-
|
I do think Debian does a horrible release policy, for the exact reasons I quoted. They waste massive amounts of ressources. I am sure you got bug fixes for the existing architecture, and those could have been part of 119. There is no need, to publish unfinished work. And I appreciate your work. |
Beta Was this translation helpful? Give feedback.
-
You are not entitled to updates. Termux 0.118 is a close to feature complete terminal emulator. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think @ShalokShalom is expressing any form of entitlement. |
Beta Was this translation helpful? Give feedback.
Because all work for app now is done by one person: @agnostic-apollo. Some changes incomplete, some not pushed.
Termux doesn't hire anyone to work on repositories, people work on it when want to do so and have time.
Be patient or use latest git version. To have frequent updates, the application part needs skilled maintainers. For now only package part has enough of them.
Btw, the readme document already states this: