Am 10.08.2026 um 16:21 schrieb Dave Fisher:
I support AOO50X and that we emphasize modern OS and dependency support which 
drives a major version release.

We also should reconsider what should be the minimum supported OSs and 
underlying dependencies.

1. macOS silicon, but what minimum version?
IMHO the one Jim posted.
2. 64 bit Windows, but what level of dev platform
imho win 10.  imho newest sdk and compilers.  I use currently 2019, but thats irrelevant.
3. Linux. Versions of RHEL and CENTOS?
We recently decided ubuntu. I would pick something that can do C++11
4. Python 3.10 or greater?
latest that we can build on all platforms.
5. Java JDK version minimum?
I would stay with java 8 for now. IMHO we are already at a scope creep.
6. What happens to FreeBSD and OS/2 downstreams?
OS/2 has not been updated in a while. I think they stopped with 4.1.11. Bitwise is a dormand construct, since it could not raise enough money. Matthias has tried to build it, but was not successfull as far as i remeber. I want to look into it, but only after we are in normal waters again. (means: our services are back online, we have development + one modern release branch. And no critical bugs like the crash bug i just fixed. And ODF 1.4 support ofc)

Best,
Dave

my 2 cents

Peter

On Aug 10, 2026, at 6:10 AM, Jim Jagielski <[email protected]> wrote:

There's been some discussion regarding whether or not the version number 4.2.x (or even 
4.5.x) is "right" for the next major version we are looking at. It's been 
suggested that maybe AOO42X be renamed to AOO50X and the respective changes also be 
applied to trunk as well.

Comments?
FWIW: I would support that effort.
--
Jim
  "This is an outrage!"
                        Tony Harrison


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to