Forum > Lazarus
We are planning the next release: Lazarus 2.0.10
Martin_fr:
The Lazarus team has scheduled
Lazarus 2.0.10
for July 2020 (estimated 4th to 11th)
This release will be built with FPC 3.2.0.
Here is the list of fixes for Lazarus 2.0.10 (since 2.0.0):
http://wiki.freepascal.org/Lazarus_2.0_fixes_branch
We would invite everyone to provide their feedback to help us improve
this upcoming release. Please let us know in particular:
- Any bug-fixes already made to trunk, that you believe should still be
merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.
Please attempt to provide your feedback by: 30th June 2020
More info on our release process can be found at (work in progress):
http://wiki.lazarus.freepascal.org/Lazarus_release_engineering
Information about the previous release:
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.4
http://wiki.lazarus.freepascal.org/User_Changes_3.2.0
The intended minimum requirements for the release will be:
Windows:
2k(*), XP(*), Vista, 7, 8, 8.1 and 10, 32 or 64bit.
FreeBSD/Linux:
gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.
macOS:
10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta), qt and qt5
(32 or 64bit).
(*) requires install from sources
Martin_fr:
For those who wonder why it is 2.0.10 and not 2.2.
We choose to make a 2.0.10 + 3.2.0 release, as this is the faster option. This release can be scheduled for early July.
A Lazarus 2.2 release would take more time to prepare. A new 2.2 fixes branch will probably need some month to stabilize, once it has been branched. That would push a release further back. A decision on 2.2 will be made in due course. More information will be posted once available.
ASerge:
--- Quote from: Martin_fr on June 22, 2020, 04:14:45 pm ---- Any bug-fixes already made to trunk, that you believe should still be
merged to the fixes branch (fixes that are not listed on the above wiki page)
--- End quote ---
35467 - TWindowProcHelper.CalcClipRgn micropatch.
34759 - For Windows there is a inconsistency in the use of wsFullScreen for WindowState.
35465 - The LCLBoundsToWin32Bounds function has two unused parameters: Width and Height.
35466 - TWin32WSCustomPage.DestroyHandle micropatch.
35694 - Micropatch of LazMethodList unit.
lucamar:
Not that my opinion matters much but ...
I know we're always wanting the "fast track" release cycle but in this particular case (lots of changes, ain't it?) I'd wait until at least next year (and not very early, at that) for a 2.2.0 release.
So this interim 2.0.10 sounds like really good news, allowing us to really check a Lazarus with FPC 3.2 without having to worry too much about checking also a brand new major version of Lazarus ;D
Frankly, I'd allow time for 2.0.10 until August or even September, to have a really fully stable last 2.0 release upon which to fall back in case of later problems.
Anyway, lotsa' thanks to all devs for their efforts. :)
Martin_fr:
--- Quote from: lucamar on June 22, 2020, 04:43:51 pm ---So this interim 2.0.10 sounds like really good news, allowing us to really check a Lazarus with FPC 3.2 without having to worry too much about checking also a brand new major version of Lazarus ;D
Frankly, I'd allow time for 2.0.10 until August or even September, to have a really fully stable last 2.0 release upon which to fall back in case of later problems.
--- End quote ---
Well there have always been a few people already testing Lazarus with the fpc fixes branch. So it is not like it is all new.
We even had some snapshots of the last 2.0.8 release with fpc fixes: https://sourceforge.net/projects/lazarus-snapshots/files/
Navigation
[0] Message Index
[#] Next page