Lazarus Release 2.0.6

[useroflazarus]

Hello. When will the Lazarus 2.0.8 be released?

[JuhaManninen]

Hello. When will the Lazarus 2.0.8 be released?

Most probably never. The energy now goes towards the next major version, Lazarus 2.2, which will be branched around the time FPC 3.2 gets released. Then there will be release candidates before the actual release.

The current fixes_2_0 branch has still got some bug fixes. You can download and build it yourself. Lazarus is very easy to build once you have FPC installed in your computer.

[Edit] Now it seems Lazarus 2.0.8 may be released after all. I don't decide such things because it mostly depends on the people actually preparing the fixes branch and building it.
It means Mattias and Martin building for different platforms and Dmitry backporting many Cocoa fixes.
This is good news as Lazarus 2.2 is still far away.

[mercurhyo]

actualy v2.07 is the version I use. it installs when you select fixes 2.0 on fpcupdeluxe 1.6.8i

[dbannon]

......
The energy now goes towards the next major version, Lazarus 2.2, which will be branched around the time FPC 3.2 gets released. Then there will be release candidates before the actual release.

And that prompts a question that has been nagging me for some time.  If we see a Lazarus 2.2.0 release, will it be based on Lazarus trunk or Lazarus fixes ?   While the process is clear in the minds of the developers, it would help people like me if it was a bit more transparent.  I have assumed every release is based on Fixes. But I see patches go into trunk that do not make it to fixes, that leaves me wondering if such patches are worthwhile ?

Davo

[PascalDragon]

It's the same for both FPC and Lazarus: the last number of x.y.z is based on a fixes branch. The second number is a new branch that's branched from trunk. E.g. 2.0.0 was branched from Lazarus trunk back then and 2.0.2 is a fixes release based on that. Trunk then became 2.1. Now 2.2.0 will be branched from trunk as well and 2.2.2 will be based on that fixes branch (and trunk will then become 2.3).

[JuhaManninen]

If we see a Lazarus 2.2.0 release, will it be based on Lazarus trunk or Lazarus fixes ?   While the process is clear in the minds of the developers, it would help people like me if it was a bit more transparent.

It is completely transparent. Every trunk revision backported to fixes_2_0 branch is listed here :
 https://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch
There is also a web interface for the actual SVN sources:
 https://svn.freepascal.org/svn/lazarus/branches/fixes_2_0/

At the bottom of the "Lazarus_2.0_fixes_branch" wiki page you find "Other branches", listing the fixes branches for other release versions.
 https://wiki.lazarus.freepascal.org/Lazarus_0.9.30_fixes_branch
 https://wiki.lazarus.freepascal.org/Lazarus_1.0_fixes_branch
 https://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch
 https://wiki.lazarus.freepascal.org/Lazarus_1.4_fixes_branch
 https://wiki.lazarus.freepascal.org/Lazarus_1.6_fixes_branch
 https://wiki.lazarus.freepascal.org/Lazarus_1.8_fixes_branch

All backported revisions are listed. How would you make it more transparent?

[dbannon]

PascalDragon's answer made it clear to me.  Thanks PascalDragon.

Juha, thanks, I am sure the information I asked for is also in the wiki page you quote. Somewhere in that page....

(I have looked at that page from time to time, at no point did I come away with the information I asked about. But I am sure its there.)

Davo

[JuhaManninen]

Juha, thanks, I am sure the information I asked for is also in the wiki page you quote. Somewhere in that page....

(I have looked at that page from time to time, at no point did I come away with the information I asked about. But I am sure its there.)

The process itself is explained here :
 https://wiki.lazarus.freepascal.org/Lazarus_Development_Process
Many details are outdated but the actual process is remains the same.