Legna wrote: ↑
Tue Mar 06, 2018 11:51 pm
Experimental because on About brackets I got
Release 1.10 experimental build 1.10.0-17483 (release 024bee940)
build timestamp: Wed Jul 05 2017 06:48:43 GMT+0000
Regarding the reason, it's more because starting from 1.11 the Linux version seems equal to Windows/macOS version as described by Adobe:
Brackets on Linux - Brackets now offers full support for the Linux platform. With an update to the shell with a new version of CEF, Brackets is now fully functional on Linux.
And I hope maybe the soft is a little bit quicker too.
I don't really need to get the latest version when it's released plus I was using Arch before Solus... Newer does not mean better but when the software is better and new functions are released it's a good reason to try.
The point is not really that "Newer does not mean better" since soon or late, packages have to be updated. It's more about the philosophy of curated
rolling release : If something is stable and works fine, there is no reason to rush on updates as the risk zero does not exists and it might cause issues or have some unwished side effects. So as long as everybody is happy the current version may remain for a while, even if newer versions are available.
This of course does not apply to everything. For example, important/core components are continuously updated or packages might be patched/updated to address vulnerabilities. Other packages updates mainly depends on the needs, the packagers and the requests.
But if someone reports that a new version of an application addresses a bug that is annoying him/her or that it brings new features/enhancements he/she is interested in, the package will be updated. This is why it is important to provide a justification and not just telling a newer versions are available.
What you explained just now is enough for requesting an update of the package on the bug tracker.