Hi all,

The Release Candidate is good for production/GA:
[X] yes / +1
[ ] no / -1

My vote is based on:
[X] binding (member of PMC)
[ ] I have built and tested the RC from source on platform [ ]
[X] I have tested the binary RC on platform [ Windows ]
[X] I have verified the source and the git hash


I have tested AOO 4.1.17m2 on:
• Windows 11 Home, 64-bit : 25H2 and 26H2
• Windows 7, 64-bit (6.1.7601 SP 1)

Two installations in each case:
• pl (full) + en-US (langpack) + SDK
• en-US (full) + pl (langpack) + SDK



Regards,
Czesław

Il giorno lun 12 ott 2026 alle ore 14:12 Marcus <[email protected]> ha
scritto:

> Am 09.10.26 um 14:00 schrieb Jim Jagielski:
> > I am calling a VOTE on releasing the source and complimentary community
> builds of Apache OpenOffice 4.1.17-RC2 (git hash 0x49c05bc6fd) as GA.
> >
> > These artifacts can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/openoffice/4.1.17-RC2/
> >
> > Please cast your vote:
> >
> > The Release Candidate is good for production/GA:
> >   [X] yes / +1
> >   [ ] no / -1
> >
> > My vote is based on:
> >   [X] binding (member of PMC)
> >   [ ] I have built and tested the RC from source on platform [ ]
> >   [X] I have tested the binary RC on platform [Windows 10]
> >   [ ] I have verified the source and the git hash
> I've tested on:
> - Windows 10 Home 64-bit Build 19045.36456
> - Installed AOO 4.1.17m2 (Build 9818 - Rev. 49c05bc6fd)
>
> - Installed "de" full install + "da" langpack
> - Switched the UI languages while testing
>
> Checksums:
> - Tested checksums for all source tarballs
> - Tested checksums for the install + langpack files de, da
>
> Document tests:
> - Existing, older DOC, XLS, PPT documents
> - Existing, older DOCX, XLSX, PPTX documents
> - Created new docs for Writer, Calc, Impress and opened / edited the
> saved file with all languages
>
> Every test without problems.
>
> Marcus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to