Recent

Author Topic: Lazarus Bugfix Release 3.8  (Read 6122 times)

mattias

  • Administrator
  • Full Member
  • *
  • Posts: 199
    • http://www.lazarus.freepascal.org
Lazarus Bugfix Release 3.8
« on: January 22, 2025, 02:56:28 pm »

The Lazarus team is glad to announce the release of Lazarus 3.8.

This is a bugfix release and was built with FPC 3.2.2.

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_3.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.2.2

Here is the list of fixes for Lazarus 3.x:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_3_0/

The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 3.8" directory.

Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#3_8

Minimum requirements:

Windows:
  2k, 32 or 64bit, Qt, Qt5, Qt6 (64bit only)

FreeBSD/Linux:
  gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, Qt6.2 for qt6, 32 or 64bit.

Mac OS X:
  Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, Qt and Qt5 (32 or 64bit), Qt6 (64bit only).

Note: Since Macos Sonoma 14 debugging takes some time to start the application, especially on first start.

The gitlab page:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_3_8

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:
https://download.lazarus-ide.org/
ftp://ftp.freepascal.org/pub/lazarus/releases/

chinaliu

  • Newbie
  • Posts: 4
Re: Lazarus Bugfix Release 3.8
« Reply #1 on: January 22, 2025, 04:31:08 pm »
thanks!

TRon

  • Hero Member
  • *****
  • Posts: 3927
Re: Lazarus Bugfix Release 3.8
« Reply #2 on: January 22, 2025, 08:04:35 pm »
This release isn't weird in any way ofc. How does the fixes of this release relate to the 4.0 RC2 release ? All testing/reports done for RC2 can be stuffed in the toilet now ?

@mattias: An unfortunate typo in the Lazarus ML about 3.6 bugfix release.
« Last Edit: January 22, 2025, 08:45:24 pm by TRon »
I do not have to remember anything anymore thanks to total-recall.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4551
  • I like bugs.
Re: Lazarus Bugfix Release 3.8
« Reply #3 on: January 22, 2025, 09:24:23 pm »
How does the fixes of this release relate to the 4.0 RC2 release ?
It does not relate. This release is built from fixes_3_0 branch while 4.0 RC2 is built from fixes_4 branch.
fixes_4 was forked from main much later. Release 3.8 does not have many changes compared to release 3.6.

Quote
All testing/reports done for RC2 can be stuffed in the toilet now ?
Why is that?
« Last Edit: January 22, 2025, 09:27:24 pm by JuhaManninen »
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

TRon

  • Hero Member
  • *****
  • Posts: 3927
Re: Lazarus Bugfix Release 3.8
« Reply #4 on: January 22, 2025, 09:29:00 pm »
Why is that?
Because when something is fixed in 3.8 while that is same issue was still present when 4.0 was forked the issue also is part of 4.0. Now, when fixed in 3.8 with this fixes release you do not expect the same issue to pop up again in 4.0 while in theory it might.
I do not have to remember anything anymore thanks to total-recall.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10788
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 3.8
« Reply #5 on: January 22, 2025, 09:32:36 pm »
In the same way that e.g. MS still updates Windows 10, even Windows 11 is out.  Just that 4.0 isn't out yet, it's just in preparation (having RCs out).

The 4.0RC has
- new features
- new bugs, that were introduced after 3.x was branched
- shared bugs that are in 4 and 3 branches (and may or may not have been fixed now)

Since some fixes were still done for the 3.0 branch, releasing 3.8 made sense. Even if we urge everyone to test the 4.0RC, at the same time it is advised that for production a 3.x is still used. So having an update to that may be helpful.

It's likely that there will not be a 3.10 as by that time 4.0 will either be out, or very nearly out. But in the end that decision depends on the feedback on the 4.0RC

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10788
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 3.8
« Reply #6 on: January 22, 2025, 09:37:52 pm »
Why is that?
Because when something is fixed in 3.8 while that is same issue was still present when 4.0 was forked the issue also is part of 4.0. Now, when fixed in 3.8 with this fixes release you do not expect the same issue to pop up again in 4.0 while in theory it might.

In theory, yes.

In practice nothing gets fixed directly in the fixes branch (unless it was introduced by some miracle only in that fixes branch / or had been unknowingly been fixed in main before).

So in 99.99% of all cases, a bug reported to any version will be fixed in the main branch (aka trunk). And then it will be merged.
Since the fixes 4 branch was created, any fix to main that would be merged to any fixes branch, would always also be merged to fixes-4.

So it is extremely unlikely that a fix gets merged to 3, but not to 4.
Mistakes do happen though. If they do, please point them out.


You can check the commits on fixes 3. The usually have "cherry picked from" remarks. You can then check that they are also present in fixes-4. And if not you can check if they should.


--EDIT

IIRC the following shows this
Code: Text  [Select][+][-]
  1.  git log --cherry --oneline  fixes_4..fixes_3_0
  2. + c6eba77be6 (HEAD -> fixes_3_0, origin/fixes_3_0) ide: updated res
  3. + a69f6e15ef docs: set version to 3.8
  4. + 57e899e4bb (tag: lazarus_3_8, build) updated makefiles
  5.  

So the only commit that is on the fixes-3 branch (since the release of 3.6) is setting the version to 3.8, and updating the res file => now those are expected to be only there.
« Last Edit: January 22, 2025, 09:46:12 pm by Martin_fr »

TRon

  • Hero Member
  • *****
  • Posts: 3927
Re: Lazarus Bugfix Release 3.8
« Reply #7 on: January 22, 2025, 09:50:30 pm »
Ok clear. Thank you for that martin and juha.

I am familiar with working with several forks being released at the same time and my experience is that in practice it usually works counterproductive to have them side by side for a longer period of time. While it might be simple for the developers (as explained) it quickly is able to become a mess for end-users because they are usually not able to figure out what belongs to what release. So you might get the same reports for both releases not to mention having to test a reported issue against the other release as well.

Although I am sure you guys have considered that it is Just something to be aware of.
I do not have to remember anything anymore thanks to total-recall.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4551
  • I like bugs.
Re: Lazarus Bugfix Release 3.8
« Reply #8 on: January 22, 2025, 10:13:14 pm »
I am familiar with working with several forks being released at the same time and my experience is that in practice it usually works counterproductive to have them side by side for a longer period of time.
I don't know why fixes_4 was forked so early. I admit I have merged bug fixes only to fixes_4 and not to fixes_3_0 while I maybe should have.
Yes, maintaining many branches and building releases from them requires extra work.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10788
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 3.8
« Reply #9 on: January 22, 2025, 10:41:06 pm »
Previous fixes branches had similar long stabilization runs.  At least recent ones (not sure there may have been an exception to one of them).

If I made no mistakes, those are the dates from git (branch creation, and tag of first release on the branch)

Code: Text  [Select][+][-]
  1.                 branch      first release
  2. fixes-4     2024-10  2025-??
  3. fixes-3     2023-06  2023-12
  4. fixes-2.2   2021-06  2022-01
  5. fixes-2.0   2018-09  2019-02
  6. fixes-1.8   2017-04  2017-12


At the time of branching, the previous fixes is at least one year old, and has lots of new feature. Many affecting existing features. So they get some time of "bug fix only" to stabilize.

jcmontherock

  • Sr. Member
  • ****
  • Posts: 277
Re: Lazarus Bugfix Release 3.8
« Reply #10 on: January 24, 2025, 09:01:41 pm »
What should we do ? Installing V 3.8 or 4.0 rc2 ?
Windows 11 UTF8-64 - Lazarus 4.0RC2-64 - FPC 3.2.2

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10788
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Bugfix Release 3.8
« Reply #11 on: January 24, 2025, 09:38:45 pm »
For production: 3.8

Additionally, if you can afford an half an hour (or maybe a bit more), then please help us (and yourself) with 4.0: Install the RC, and test your (backed up or exported) projects with it.
I.e., 4.0RC is for testing the upcoming 4.0.
If you test the RC, then you are more likely to have a smooth transition when it is released.

Thanks.

Jonax

  • New Member
  • *
  • Posts: 24
Re: Lazarus Bugfix Release 3.8
« Reply #12 on: January 31, 2025, 01:25:24 pm »
Just spawned a Debian VM for the purpose of trying the 3.8.
Works fine, of course.
Hope to find time to try the 4.0 RC2 later.

 

TinyPortal © 2005-2018