We are planning the next release: Lazarus 2.0.12

[Martin_fr]

The Lazarus team has scheduled

      Lazarus 2.0.12
      for February 2021 (estimated 22nd to 25th)

      This release will be built with FPC 3.2.0.

Here is the list of fixes for Lazarus 2.0.12 (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: 16th February 2021


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

[tetrastes]

The issue https://forum.lazarus.freepascal.org/index.php?topic=52808 remains in fixes.
Compile the project for LCLwin32 widgetset, launch and click ToggleBox - ComboBox "flickers" (white box appears in the ComboBox for a time of Sleep(), approximately the size of the focus rectangle, but in other my programs it can be the size of the whole ComboBox).
This is regression since Lazarus 2.0.8.

[AlexTP]

>macOS:    10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta),

Cocoa is not beta now (IDE has dropped this mark).

[Martin_fr]

The issue https://forum.lazarus.freepascal.org/index.php?topic=52808 remains in fixes.
Compile the project for LCLwin32 widgetset, launch and click ToggleBox - ComboBox "flickers" (white box appears in the ComboBox for a time of Sleep(), approximately the size of the focus rectangle, but in other my programs it can be the size of the whole ComboBox).
This is regression since Lazarus 2.0.8.

Unfortunately there is no mention when it was fixed in trunk. So no info where to look what to backport (nor if it even could be backported).
If indeed it is fixed in trunk, then that means the fix will be in Lazarus 2.2

[del]

Keep up the great work !!! 

[Al-Eid]

Thank you and good luck

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

In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.

[Martin_fr]

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

In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.

In principal yes. Practical there are limits. Some fixes make massive changes and/or may relay on code of new features. Merging it may carry a high risk of breaking code, rewriting it may be a lot of work. Also some fixes may carry a risk of breaking other stuff, then they may not be merged, or only be merged if they had been tested long enough.

The "that you believe" is not about whether a fix should be merged, but rather whether anyone believes a fix has not yet been merged. (Of course that includes, any fix of which someone knows for sure that it wasn't yet merged).
In that sense, any un-merged bug-fix can be brought forward. It will then - time allowing - be evaluated for merging. (Time allowing: That is the committer for each revision needs to be looked up, contacted, and they needs to decide).

[ASerge]

But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.

[JuhaManninen]

But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.

Of  course it will be released in the next major version 2.2.

[Roelof]

Very nice indeed!

[Sieben]

We would invite everyone to provide their feedback to help us improve this upcoming release.

Sorry for missing this thread 'til now, but it might still be the right place to leave a note that TSynEdit does not publish OnContextPopup and OnResize yet, and same for T/DB/DateTimePicker with OnShowHint - cf here as well. If not for this then maybe for the next release.

[Martin_fr]

Sorry for missing this thread 'til now, but it might still be the right place to leave a note that TSynEdit does not publish OnContextPopup and OnResize yet, and same for T/DB/DateTimePicker with OnShowHint - cf here as well. If not for this then maybe for the next release.

I made a note, probably will still get it in.

Not sure that patch fixes the issue for SynEdit?
If not, then make a new bug report for SynEdit, please. (no patch required, just need a reminder)

[Sieben]

Not sure that patch fixes the issue for SynEdit?

I did not include it in my patch - which was not applied, however - and afaik wp did not include it either. Anyway, events still missing in current rev 64617.

Reminder created as issue 38511.

[Martin_fr]

Reminder created as issue 38511.

Fixed and merged. Merged the commit for the other components too.

Even though it was just half a day. Busy day, ant at the end of the day one last look at the bugtracker....