Home » Community » U++ community news and announcements » 2025.1.1rc1
|
|
Re: 2025.1.1rc1 [message #61728 is a reply to message #61723] |
Fri, 04 July 2025 11:25   |
Tom1
Messages: 1305 Registered: March 2007
|
Ultimate Contributor |
|
|
Hi Mirek,
A quick check suggests that it works here.
Please note that the license agreement shown during installation still states last year:
"Copyright © 1998, 2024 U++ team"
Best regards,
Tom
|
|
|
Re: 2025.1.1rc1 [message #61729 is a reply to message #61728] |
Fri, 04 July 2025 18:54   |
 |
Klugier
Messages: 1102 Registered: September 2012 Location: Poland, Kraków
|
Senior Contributor |
|
|
Hello Tom,
I won't change that, it is a hotfix release with critical changes. From my point of view, it is very cosmetic issue and it won't influence user experience in anyway. If we will look what we fixed since release, there will be more important things to pick. So, I will leave it as it is and focus to fix it on main and then on the new release.
Klugier
U++ - one framework to rule them all.
[Updated on: Fri, 04 July 2025 18:54] Report message to a moderator
|
|
|
Re: 2025.1.1rc1 [message #61730 is a reply to message #61729] |
Fri, 04 July 2025 22:40   |
Tom1
Messages: 1305 Registered: March 2007
|
Ultimate Contributor |
|
|
Hi Klugier,
Absolutely! It's all up to you how you wish to proceed with that. I just felt I should let you know about it. Personally, I do not have any preference...
Best regards,
Tom
|
|
|
|
|
Re: 2025.1.1rc1 [message #61735 is a reply to message #61723] |
Thu, 17 July 2025 21:17   |
Oblivion
Messages: 1216 Registered: August 2007
|
Senior Contributor |
|
|
Hi,
Quote:Hello Mirek,
I saw that there is a compilation issue on older Linux distributions due unable to handle new AES stuff. I am also aware that you comited workaround to fix this problem. What should we do in context of release? Should we proceed with 2025.1.1 and then release proper fix with 2025.1.2 or should we wait and fix this issue. I think we shouldn't wait with 2025.1.1 the fastest we release the batter. The addressed issues are critical.
AES-GCM & "Secure" stuff is meant for release >= 2025.2. 2025.1.x shouldn't ship it.
I'm working on a proper workaround (it will be available as late as next week) for the compilation issue on older linux distros.
Best regards,
Oblivion
Github page: https://github.com/ismail-yilmaz
Bobcat the terminal emulator: https://github.com/ismail-yilmaz/Bobcat
[Updated on: Thu, 17 July 2025 21:19] Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Sat Jul 26 03:54:02 CEST 2025
Total time taken to generate the page: 0.03316 seconds
|