Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)

[piola]

Where did you see the announcement?

Latest News

November 28th, 2017

 FPC version 3.0.4 has been released!

This version is a point update to 3.0 and contains bugfixes and updates packages, some of which are high priority.

There is a list of changes that may break backward compatibility. You can also have a look at the FPC 3.0.4 documentation.

[JuhaManninen]

Latest News
November 28th, 2017
 FPC version 3.0.4 has been released!
...

Indeed, the www.freepascal.org page already has an announcement. Looks promising!
However there is nothing to download yet. I believe we get more announcements when the actual installation packages are copied.

[FTurtle]

However there is nothing to download yet.

Some links are not corrected yet but downloads are ready.
In particular:
https://sourceforge.net/projects/freepascal/files/Win32/3.0.4/
https://sourceforge.net/projects/freepascal/files/Mac%20OS%20X/3.0.4/

[dbannon]

FPC 3.0.4 has finally been released 

So I hope we can look forward to the wishfully awaited Lazarus 1.8 soon 

Indeed !  (but I hope the memory leak in OSX, TrayIcon is fixed first, memory leaks are evil!) 

And I just got my cross platform auto build (for my app) working too. I'll have to start again....  But yep, its great to see things moving here.

 

[JuhaManninen]

Indeed !  (but I hope the memory leak in OSX, TrayIcon is fixed first, memory leaks are evil!) 

Are you saying we should delay Lazarus 1.8 release until one OSX related bug is fixed? What about the other 1729 open Lazarus issues? Maybe they should be fixed before a release, too.

Actually clear bug fixes can still be merged to the 1.8 release. If a patch fixes a memory leak and does not break anything, it can be included. ... but hurry up, the patch is needed quickly.

[BeniBela]

Indeed !  (but I hope the memory leak in OSX, TrayIcon is fixed first, memory leaks are evil!) 

Better a TrayIcon leak than a TrayIcon crash

It was not merged in fixed branch either

[JuhaManninen]

Better a TrayIcon leak than a TrayIcon crash
It was not merged in fixed branch either

I marked it for merging now.
 http://wiki.lazarus.freepascal.org/Lazarus_1.8_fixes_branch

[dbannon]

Better a TrayIcon leak than a TrayIcon crash

Hmm, maybe consider that a memory leak can crash your whole machine, not just the app ?   And it sounds like 32258 is hard to reproduce and may not bite everyone. On the other hand, 32678 is trivial to reproduce and makes an official LCL component unusable. You cannot use the TrayIcon on OSX without suffering the leak.

[JuhaManninen]

... And it sounds like 32258 is hard to reproduce and may not bite everyone. On the other hand, 32678 is trivial to reproduce and makes an official LCL component unusable.

There is one huge difference between issues 32258 and 32678:
32258 is fixed but 32678 is not. That is why the fix for 32258 can be merged but a fix for 32678 cannot.
Convincing us that the bug is evil does not change anything.
As I wrote a valid patch can still be applied and merged. Hurry up if you want it included.

[dbannon]

...a valid patch can still be applied and merged. Hurry up if you want it included.

me ?  Please check the left hand side bar. "Jr. Member", you would have to be crazy to accept a patch from me. To make matters worse, Mac is my least familiar platform.

But seriously JuhaManninen, are you saying that bug reports without an accompanying patch will probably be disregarded ?

davo

[JuhaManninen]

me ?  Please check the left hand side bar. "Jr. Member", you would have to be crazy to accept a patch from me.

It would be accepted if it works and does not break anything else.
Your number of posts in this forum has no relevance.

To make matters worse, Mac is my least familiar platform.

Then don't use it.

But seriously JuhaManninen, are you saying that bug reports without an accompanying patch will probably be disregarded ?

Yes if nobody wants to fix it. This is a FOSS project based on voluntary work. Nobody gets paid. Basically every contributor "scratches his own itch" as the saying goes.
However you could try to speed up a specific feature or bug fix by offering a bounty.
 http://wiki.lazarus.freepascal.org/Bounties
Paid development in a FOSS project is possible and perfectly OK. Some projects have paid developers sponsored by commercial companies. We don't.

[Martin_fr]

are you saying that bug reports without an accompanying patch will probably be disregarded ?

Well no, if a bug can be reproduced it will not be "disregarded".

But there are no paid workers, to whom bugs can be assigned by some priority. All bug fixes are done by volunteers.

So the bug will be in the bugtracker, until a volunteer picks it up.

[soerensen3]

Wow the package for arch was updated really fast. https://www.archlinux.org/packages/community/x86_64/fpc/
However if I try to update it will tell me it is already the newest version:

Code: Bash  [Select][+][-]

1. $ sudo pacman -Syy fpc-src fpc
2. :: Synchronizing package databases...
3.  core                     137,8 KiB   811K/s 00:00 [######################] 100%
4.  extra                   1772,5 KiB  1441K/s 00:01 [######################] 100%
5.  community                  4,4 MiB  2,13M/s 00:02 [######################] 100%
6.  multilib                 178,7 KiB  4,36M/s 00:00 [######################] 100%
7. warning: fpc-src-3.0.2-2 is up to date -- reinstalling
8. warning: fpc-3.0.2-1 is up to date -- reinstalling
9. ...
10.  

Does anyone have the same problem?

[JuhaManninen]

Wow the package for arch was updated really fast. https://www.archlinux.org/packages/community/x86_64/fpc/

That is a FPC 3.0.4 package but this thread is about Lazarus Release Candidate.
Please open a new thread about FPC release. You have better chance to get answers, too.

[soerensen3]

@JuhaManninen:
Yes, you're right but there was no fpc 3.0.4 announcement yet and I was kind of lazy I guess. 
I opened a new thread: http://forum.lazarus.freepascal.org/index.php/topic,39110.msg267269/topicseen.html#new