Recent

Author Topic: We are planning the next release: Lazarus 2.0.2  (Read 35433 times)

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
We are planning the next release: Lazarus 2.0.2
« on: April 03, 2019, 06:35:39 pm »
The Lazarus team is glad to announce that:

      The release of Lazarus 2.0.2

has been scheduled for around

      16th to 18th April 2019

This release will be built with FPC 3.0.4.
The previous release Lazarus 2.0.0 was built with FPC 3.0.4 as well.

Here is the list of fixes for Lazarus 2.0.2 (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 as know in particular:
- Any fixes 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 last release
- Other urgent matters, you believe we should know before the release.

Please attempt to provide your feedback by: 10th April 2019

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

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.

Mac OS X:
   10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta), qt and qt5 (32 or 64bit).

lucamar

  • Hero Member
  • *****
  • Posts: 4219
Re: We are planning the next release: Lazarus 2.0.2
« Reply #1 on: April 03, 2019, 07:06:33 pm »
Any reason for a new release so soon after the previous? I mean, it has been less than two months since versoin 2.0.0

Not that I'm complaining, mind you; I'm just curious.
Turbo Pascal 3 CP/M - Amstrad PCW 8256 (512 KB !!!) :P
Lazarus/FPC 2.0.8/3.0.4 & 2.0.12/3.2.0 - 32/64 bits on:
(K|L|X)Ubuntu 12..18, Windows XP, 7, 10 and various DOSes.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.2
« Reply #2 on: April 03, 2019, 08:54:30 pm »
No particular reason.

Those are the dates tagged in mantis (they may not be exact to the day, and not sure if older ones are correct)
Code: [Select]
2.0    2019-02-05
1.8.6  2018-08-01
1.8.4  2018-05-21
1.8.2  2018-03-01
1.8    2017-12-05
1.6.4  2017-03-01
1.6.2  2016-11-15
1.6    2016-02-18
1.4.4  2015-10-05
1.4.2  2015-07-14
1.4    2015-04-20
1.2.6  2014-10-12
1.2.4  2014-06-15
1.2.2  2014-04-21
1.2.0  2014-03-01
1.0.14 2013-11-15
1.0.12 2013-08-24
1.0.10 2013-03-26
1.0.8  2013-03-01
1.0.6  2013-02-01
1.0.4  2012-10-05
1.0.2  2012-09-29
1.0.0  2012-08-28

So we used to have a 2 to 3 month cycle before. Though the cycle will vary depending on how we have time. (There should have been a 1.8.8, but we were busy preparing 2.0)

Last release was early Feb, so it will be 2.5 month. And we do have a nice amount of fixes, so it would be good to make them available.

lucamar

  • Hero Member
  • *****
  • Posts: 4219
Re: We are planning the next release: Lazarus 2.0.2
« Reply #3 on: April 03, 2019, 09:59:28 pm »
So we used to have a 2 to 3 month cycle before.

Oh, I guess I've been mislead by my own update cycle, which used to be between 6 months to one year. No wonder I always missed the X.Y.0 releases :D
Turbo Pascal 3 CP/M - Amstrad PCW 8256 (512 KB !!!) :P
Lazarus/FPC 2.0.8/3.0.4 & 2.0.12/3.2.0 - 32/64 bits on:
(K|L|X)Ubuntu 12..18, Windows XP, 7, 10 and various DOSes.

fcu

  • Jr. Member
  • **
  • Posts: 89
Re: We are planning the next release: Lazarus 2.0.2
« Reply #4 on: April 03, 2019, 10:48:45 pm »
i hope you remove the flickering caused by the splitter component

Oscar Vazquez

  • New Member
  • *
  • Posts: 11
Re: We are planning the next release: Lazarus 2.0.2
« Reply #5 on: April 03, 2019, 11:59:47 pm »
Excellent, when they enabled the Contrains to use them at the Tfield level in the data module.
https:/?/joinchat/IbmDtw88init_yo3ArCJqg

Chat de Telegram Lazarus

BeniBela

  • Hero Member
  • *****
  • Posts: 905
    • homepage
Re: We are planning the next release: Lazarus 2.0.2
« Reply #6 on: April 04, 2019, 12:40:47 am »
Perhaps someone can find a fix for https://bugs.freepascal.org/view.php?id=27401 ?

ASBzone

  • Hero Member
  • *****
  • Posts: 678
  • Automation leads to relaxation...
    • Free Console Utilities for Windows (and a few for Linux) from BrainWaveCC
Re: We are planning the next release: Lazarus 2.0.2
« Reply #7 on: April 04, 2019, 01:00:18 am »
1.8.6  2018-08-01

Was there actually a 1.8.6 release?  I thought we only got up to 1.8.4 before 2.0?
-ASB: https://www.BrainWaveCC.com/

Lazarus v2.2.7-ada7a90186 / FPC v3.2.3-706-gaadb53e72c
(Windows 64-bit install w/Win32 and Linux/Arm cross-compiles via FpcUpDeluxe on both instances)

My Systems: Windows 10/11 Pro x64 (Current)

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.2
« Reply #8 on: April 04, 2019, 04:36:47 am »
1.8.6  2018-08-01

Was there actually a 1.8.6 release?  I thought we only got up to 1.8.4 before 2.0?
The tags in mantis are created in advance. They always go one step further. This is so bug-targets can be set for future releases.

When a future minor release is replaced by a new major released, the correct thing would be to move any issue from that tag, to the new major tag. And then remove the no longer needed tag.
But no one has yet bothered to go through that work...



About individual issues mentioned in other posts above:
Please find the relevant issue report on Mantis https://bugs.freepascal.org/ and check if they are resolved. Mantis should tell you the revision, and that allows you to check http://wiki.freepascal.org/Lazarus_2.0_fixes_branch if the fix will be in 2.0.2

If an issue is not reported on Mantis, then please add it there.

dsiders

  • Hero Member
  • *****
  • Posts: 1052
Re: We are planning the next release: Lazarus 2.0.2
« Reply #9 on: April 04, 2019, 11:08:55 am »
Any chance we'll see updated Help builds for the release?

LCL and LazUtils online (SourceForge) are at version 0.9.3.
LCL and LazUtils CHMs are at version 1.2.4.6. (Windows Installer for Lazarus 2.0.0).

Sure would be nice to get something more recent.
Preview Lazarus 3.99 documentation at: https://dsiders.gitlab.io/lazdocsnext

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.2
« Reply #10 on: April 04, 2019, 01:54:37 pm »
I am aware that the ones at sourceforge are outdated.

I am trying to find out how my chm viewer can be made to show the version (I seem to only have the file date)

lcl and lazutils were rebuild before the release was made https://svn.freepascal.org/svn/lazarus/binaries
And the installer seems to have the same version of files.

dsiders

  • Hero Member
  • *****
  • Posts: 1052
Re: We are planning the next release: Lazarus 2.0.2
« Reply #11 on: April 04, 2019, 11:41:24 pm »
I am aware that the ones at sourceforge are outdated.

I am trying to find out how my chm viewer can be made to show the version (I seem to only have the file date)

lcl and lazutils were rebuild before the release was made https://svn.freepascal.org/svn/lazarus/binaries
And the installer seems to have the same version of files.

The only mechanism I can find is to look at the generated documentation for the lcl_version and laz_version topics. In the chms, lcl_Version contains '1.2.4.6'. And those were installed, as I mentioned, with the Windows installler for Lazarus 2.0.0.

I vote for putting the version info in the page footer for generated pages.

EDIT:

I just looked again. I was wrong, lcl_version is actually 1.0.12.

EDIT:

I downloaded the separate zip file with Doc. It is in fact at version '1.8.5.0'. So that's good. But not having them in the installer isn't.
« Last Edit: April 05, 2019, 12:10:21 am by dsiders »
Preview Lazarus 3.99 documentation at: https://dsiders.gitlab.io/lazdocsnext

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.2
« Reply #12 on: April 05, 2019, 12:54:08 am »
The version example in the help text is not automatically updated.

From the file docs/xml/lcl/lclversion.xml (that is one of the source file from which the help is build)
Code: [Select]
<p>For example, if the LCL version is 1.2.4.6, lcl_fullversion will be 1020406</p>
That is the text that goes into the help. Even for trunk. It is still correct. It is an example, so it does not have to be the current version.

The 1.0.12 is in the same file, as is 0.9.25

Quote
I downloaded the separate zip file with Doc. It is in fact at version '1.8.5.0'. So that's good. But not having them in the installer isn't.
And that number appears at text, in the same location as the 1.2.4.6?

dsiders

  • Hero Member
  • *****
  • Posts: 1052
Re: We are planning the next release: Lazarus 2.0.2
« Reply #13 on: April 05, 2019, 01:19:56 am »
The version example in the help text is not automatically updated.

From the file docs/xml/lcl/lclversion.xml (that is one of the source file from which the help is build)
Code: [Select]
<p>For example, if the LCL version is 1.2.4.6, lcl_fullversion will be 1020406</p>
That is the text that goes into the help. Even for trunk. It is still correct. It is an example, so it does not have to be the current version.

The 1.0.12 is in the same file, as is 0.9.25

Quote
I downloaded the separate zip file with Doc. It is in fact at version '1.8.5.0'. So that's good. But not having them in the installer isn't.
And that number appears at text, in the same location as the 1.2.4.6?

The file at https://svn.freepascal.org/svn/lazarus/binaries/docs/chm/ has the following:

Code: [Select]
lcl_version
LCL version string

Declaration
Source position: lclversion.pas line 46

const lcl_version = laz_version;

Description
Contains the LCL version string, e.g. 1.0.12.

I am assuming this is is the same file used in the installer build.

The zip file at SourceForge contains:

Code: [Select]
lcl_version
LCL version string

Declaration
Source position: lclversion.pas line 40

const lcl_version = '1.8.5.0';

Description
Contains the LCL version string, e.g. 1.0.12.

Which has a real value for the constant.

The installed version being older (or even different) than the zip file on SourceForge is an issue. Most folks are using what gets installed.
 
The online help is a different matter altogether.

Preview Lazarus 3.99 documentation at: https://dsiders.gitlab.io/lazdocsnext

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: We are planning the next release: Lazarus 2.0.2
« Reply #14 on: April 05, 2019, 02:31:04 am »
In that case th zip is outdated.

Revision: 57504
Date: 14 March 2018 09:21:54
LazUtils: Add unit LazVersion. Use it also for LCLVersion. Issue #33418,

Back then (that was Lazarus 1.9 svn) the unit was changed. The actual number is now stored in laz_version, and lcl_version became a forwarder.

So the doc for lcl_version should show
Code: Pascal  [Select][+][-]
  1. const lcl_version = laz_version;
as the correct declaration.

---

The reason this is a bit tricky to discuss is: I do build the win installer, but not the docs. However the person who does build the docs had notified me before the 2.0.0 release that they were updated in svn. And the win installer contains the files from svn.

So the only knowledge I had on the docs was his word. I trust that, but it does not mean an error could not have happened along the way.
I did enquire with him, but had not yet gotten a response.

It now seems the doc zip needs updating.
I don't know if a footer with the version could be added to the docs. So I can't currently comment on how to make it easier to check their version...

 

TinyPortal © 2005-2018