How often to install new TSE version

[Fred H Olson]

I use TSE a lot. It, with my extensions, forms the basis for much of
how my computer is organized - mostly as text files. While I appreciate
and applaud the active development, I primarily USE TSE. For daily use
I do not install, configure and customize a new TSE version very often
- certainly not every time a new version that is available. I
currently use:

The SemWare Editor (Linux) 4.50 - 2024 Oct 26

TSE is very configurable and extensible and I do a lot of that.
Re-installing seems like a hassle. Particularly merging changes
to tse.ui into my .ui. Probably more a psychological than real hurdle.
I rationalize with 'if it is not (badly) broken, dont fix it (yet)'

I may install a new version beside / independent of my regular version
to try something. This is a bit awkward because my fingers want to use
my key assignments that are different than in tse.ui.


Many open source programs declare "stable" releases.

Does / could TSE have regular designation of "stable" or major releases?
Did the version number 4.50 have such an implecation.
Is 4.60 or even 5.0 anticipated?

Such a designation might be enough to get me to install and configure it.

I asked ChatGPT:
How often does open source software have "stable" versions? The reply:

There isn't a single schedule for when open-source software releases
"stable" versions. It varies widely depending on the project, its
size, and its development philosophy.

Some common patterns:
Project type Typical stable release frequency
Large operating systems Every 6-24 months
Major programming languages Every 1-12 months
Popular applications Every few weeks to several months
Small volunteer projects Irregular-sometimes years between releases
Rolling-release projects No fixed stable versions; updates are continuous

Examples:

Linux kernel releases stable kernel versions roughly every 2-3
months, with long-term support (LTS) versions periodically.

Ubuntu publishes a regular release every six months and an LTS release
every two years.

Python typically releases a new major version annually.

Mozilla Firefox ships stable releases about every four weeks.

Open-source projects often use labels such as:
Alpha: early testing, many changes expected.
Beta: feature-complete but still being tested.
Release Candidate (RC): expected to become stable unless
significant bugs are found.
Stable: intended for general users and production use.
LTS (Long-Term Support): stable version supported with security
and bug fixes for an extended period.

A key difference from commercial software is that many open-source
projects release when maintainers feel the software is ready rather
than on a strict calendar. As a result, some projects may publish
stable releases every month, while others may go several years between
stable versions.

Fred

--
Fred H. Olson Minneapolis,MN 55411 USA (near north Mpls)
Email: fholson at cohousing.org 612-588-9532
My Link Pg: http://fholson.cohousing.org A1l_