U++ forum: Welcome to the forum

Search on this site

Search in forums

Home » Community » U++ community news and announcements » 2025.1.1rc1

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

2025.1.1rc1 [message #61723]

Thu, 03 July 2025 11:10

mirek
Messages: 14267
Registered: November 2005

Ultimate Member

Fixes CLANG 20 warning about Moveable and fedora assist crashes:

https://sourceforge.net/projects/upp/files/upp/2025.1.1rc1/

Please test, if there are no complaints I will make it default in ~10 days.

[Updated on: Thu, 03 July 2025 18:09]

Report message to a moderator

Re: 2025.1.1rc1 [message #61724 is a reply to message #61723]

Thu, 03 July 2025 17:55

Didier
Messages: 736
Registered: November 2008
Location: France

Contributor

Still fine for me Smile

Report message to a moderator

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

Report message to a moderator

Re: 2025.1.1rc1 [message #61729 is a reply to message #61728]

Fri, 04 July 2025 18:54

Klugier
Messages: 1106
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

Report message to a moderator

Re: 2025.1.1rc1 [message #61733 is a reply to message #61723]

Thu, 17 July 2025 20:35

Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

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.

Klugier

U++ - one framework to rule them all.

Report message to a moderator

Re: 2025.1.1rc1 [message #61734 is a reply to message #61733]

Thu, 17 July 2025 21:06

mirek
Messages: 14267
Registered: November 2005

Ultimate Member

Klugier wrote on Thu, 17 July 2025 20:35

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.

Klugier

AES is post 2025.1 (AFAIK - please check).

Report message to a moderator

Re: 2025.1.1rc1 [message #61735 is a reply to message #61723]

Thu, 17 July 2025 21:17

Oblivion
Messages: 1226
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

Re: 2025.1.1rc1 [message #61736 is a reply to message #61735]

Thu, 17 July 2025 22:04

Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello,

Thanks. So, I think we can move forward with releasing 2025.1.1. It is now older than 10 days Smile

Klugier

U++ - one framework to rule them all.

[Updated on: Thu, 17 July 2025 22:48]

Report message to a moderator

Re: 2025.1.1rc1 [message #61755 is a reply to message #61736]

Tue, 29 July 2025 00:04

Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello Mirek,

I think you can make renmae 2025.1.1rc1 to 2025.1.1 on Sourceforge and make it official release. Once done, I will create release on GitHub and then update flatpak. Instead of having 10 days, now e almost have 30...

Klugier

U++ - one framework to rule them all.

[Updated on: Tue, 29 July 2025 00:05]

Report message to a moderator

Re: 2025.1.1rc1 [message #61758 is a reply to message #61755]

Tue, 29 July 2025 13:32

mirek
Messages: 14267
Registered: November 2005

Ultimate Member

Sorry, I thought I already did... Done.

Report message to a moderator

Re: 2025.1.1rc1 [message #61759 is a reply to message #61758]

Tue, 29 July 2025 18:51

Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello Mirek,

Thanks! I created 2025.1.1 release on GitHub. Alos, I updated documentation on the stable release in this commit. Should we merge stable to main or cherry pick this commit? I am affraid of potential conflicts in the future.

Klugier

U++ - one framework to rule them all.

Report message to a moderator

Re: 2025.1.1rc1 [message #61760 is a reply to message #61759]

Wed, 30 July 2025 00:40

superdev
Messages: 32
Registered: August 2022

Member

Klugier wrote on Tue, 29 July 2025 18:51

Hello Mirek,

Thanks! I created 2025.1.1 release on GitHub. Alos, I updated documentation on the stable release in this commit. Should we merge stable to main or cherry pick this commit? I am affraid of potential conflicts in the future.

Klugier

17810?

Win7x64, upp-win-17799

Report message to a moderator

Re: 2025.1.1rc1 [message #61761 is a reply to message #61760]

Wed, 30 July 2025 22:01

Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello superdev,

It's fine, for GitHub releases I don't use commit number version in the release title. IMO, It doesn't present well. The only reference to this version is on the files associated with release.

Klugier

U++ - one framework to rule them all.

Report message to a moderator

Previous Topic:	SecureBuffer and SecureZero support
Next Topic:	GIT release tag naming convention has been changed

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Aug 23 14:59:20 CEST 2025

Total time taken to generate the page: 0.04235 seconds