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]

- 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)

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 

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]

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 

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.

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/

[Zoran]

Not that my opinion matters much but ...

...

Please note that FPC 3.2 is not quite some new strange territory for Lazarus.
Although Lazarus is always officially released with released FPC version, Lazarus (both trunk and 2.0 fixes) has been tested and used with fpc 3.2. since it was branched (almost two years ago) and especially since release candidate came out couple of months ago.

[lucamar]

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.

Please note that FPC 3.2 is not quite some new strange territory for Lazarus.

Yes, I know, even "played" a little with those "previews". But an "official" release is something a little diffferent, as both of you know

Remember that we are not "aficionados" but program in Pascal for a (rather bare ) living and have a pletora of prettty medium to big business applications.

[marcov]

Will 2.0.10 still support 3.0.4 ?

[Martin_fr]

Will 2.0.10 still support 3.0.4 ?

It should.
Lazarus should always support at least one version back.
So the question would be for 3.0.2

[lelebass]

- 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)

r63297 - https://bugs.freepascal.org/view.php?id=37127

Daniele

[Ullman]

Hi there,
so is the mentioned release a beta with a beta undercarriage?
I have not seen any proclamation of fpc 3.2 on its homepage so far.

[trev]

Hi there,
so is the mentioned release a beta with a beta undercarriage?
I have not seen any proclamation of fpc 3.2 on its homepage so far.

From the Free Pascal website homepage:

Latest News

June 19th, 2020

    FPC version 3.2.0 has been released!

[Ullman]

Your right - updating the browser cache sometimes help 

[dbannon]

....
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.

I have been building tomboy-ng with FPC320 beta and Lazarus Trunk for last two releases.  Looks good ....

Davo

[marcov]

Will 2.0.10 still support 3.0.4 ?

It should.
Lazarus should always support at least one version back.
So the question would be for 3.0.2

Oh. Big motivation to start working on 3.2.2 :-)