Hi,

Am 04.01.2026 um 11:13 schrieb Matthias Seidel:
Hi Peter, All,

Happy New Year!

Am 02.01.26 um 15:26 schrieb [email protected]:
Happy New Year @all,


A new year is in the house and I thought we try something this year. A roadmap.
+1 for a roadmap!
yes. If people see or plan to work on different topics, then please speak up. Then we have a more transparent view where we are moving

This is open for discussion, and I thought this are the topics we should try to tackle this year. What is your opinion?

Apache OpenOffice:

- 4.2

 -- Get an actual translation import

--  fix remaining blockers

This should have priority.

Getting the translation working again and then we can release a 4.2.0-dev6 build. After all the years, we should really switch to 4.2.0 and release it finally.

Looking at the AOO41X branch, it looks stalled. So I assume that no release is planned?
If possible i would avoid another 41X release. I see only security that could come up with the need of one more Version if we are to slow stabilizing 42x

Personally, I will concentrate on AOO42X.

Regards,

   Matthias


- 4.3 Test Version

I thought about this I think we should end 4X with 42X, because:

-- move to C++11 as min version for code.
we need to bumb C++ version for Mac Silicon build. Claude AI provides following possible impact:

*Compiler ABI Changes*

- Different name mangling schemes in some cases

- Different vtable layouts

This could break UNO if used in an extension. Not sure but we should bumb to Version 5.0.0 even if we do not change a lot in code.


--  Win 64 Version

--  Mac Silicon build (deadline fall 2027)

Infrastructure

- Translation service

-- Manual driven ci/cd process

-- test Version for weblate

-- migration away from the server to a docker setup

-- prod migration from Pootle to weblate

- Wiki update

-- build a test instance for development, with the ability to refresh from prod

-- update test with latest mwiki version.

-- prod update

- Extension Website

-- create concept

-- create a PoC



---------------------------------------------------------------------
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