Am 07.06.2026 um 15:21 schrieb Pedro Lino via dev:
Hi Peter, all
Given the relevance, I think that it is not simply a bug fix release. It should
be a 0.1 point release meaning it should be released as version 4.2.0.
In my opinion, we should delete the current 42X branch (there is nothing unique
there, it was just branched a long time ago), make a copy of 41X, cherry pick
Jim's new code to that branch and rename it to 42X.
Just to be sure we are on the same page.
The changes Jim did require that we update windows to win 64, update all
windows binding to a newer Version, and update all mac coca to the
minimum sdk. That is a must do to use the changes.
This means that we are not able to do a 4.1.17 release because mac will
not build. We can not build a windows release because we are not able to
build python 3.1 with the VS2008 compiler. If we build with python 2.7
the migrated scripts will not work.
Linux will go ahead if we add python 3
same goes for 4.2.
Once we have versions that are updated then extension written in python
will fail, because they are written for python 2.7 not for python 3. C++
extensions will fail because we will move to newer sdks probably raise
the C++ standard. (newest Apple sdks will want newer C++ standard.) So
these will fail.
Jims change will bring us back into the now, but with them break a lot
of stuff that we have. That is why i suggest to push the version in
trunk from currently 4.5 to 5. As i have described in the roadmap :)
We need to capture the momentum where more Office suites not coming from big
private companies are in high demand... This is particularly true for Open
Source based software
Later, we can re-branch for 43X (or 50X) which hopefully will incorporate new
translations and all the new stuff which is already in trunk...
All the best,
Pedro
On 06/07/2026 1:19 PM WEST [email protected] wrote:
Hi all,
Does it make sense that we have these changes in the branch now?
Ii suggest to revert these changes and push the version number on trunk
to 500.
I think this is the impact of Jims awesome work.
All the best
peter
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
