[Lazarus] FPC 2.4.2 and Lazarus

[Rigel Rig]

   >This is exactly the point I was trying to get across. I for one do not
 >use Trunk as much as I did in the past. Simply because I am losing a
 >lot of productivity in my day-to-day work fighting with bugs that did
 >not exist before. Similar issue apply to FPC trunk... 


I agree with that. 

When ready version of Lazarus, appears a new version of GTK or QT, with new bugs, which affect Lazarus. The new version of Lazarus fix them, but appears a new version of GTK or QT and the cycle continues indefinitely. Or computer have a new version of GTK or QT, which Lazarus don't discover them. Most mails in this list are due to problems with GTK or QT.
Do you know what is latest version of Lazarus, using only FPC without Gtk or QT?
 
 
 >От:  Graeme Geldenhuys  
 >Относно: Re: [Lazarus] FPC 2.4.2 and Lazarus
 >До: Lazarus mailing list  
 >Изпратено на: Сряда, 2010, Май 19 20:39:24 EEST

 >On 19 May 2010 17:48, Martin wrote:
 >> As it stands currently, I am not 100% convinced, that not quite some of them
 >> may only be reported *after* the next release (Since not every user uses
 >> trunk).
 >
 >This is exactly the point I was trying to get across. I for one do not
 >use Trunk as much as I did in the past. Simply because I am losing a
 >lot of productivity in my day-to-day work fighting with bugs that did
 >not exist before. Similar issue apply to FPC trunk.
 >
 >I report 90% of what I find, but I fear other see me then as a nagging
 >person always finding fault. This is unfortunate. Maybe it's just
 >because I use Lazarus IDE in a commercial environment, and not as a
 >hobby (like most developers here - I think). When I do use Trunk I
 >don't expect everything to work, but I also don't expect so many
 >regression bugs. Instead I would expect new features to have bugs, not
 >old/existing features.
 >
 >
 >> release. Some form of pre-release, but I think no one (who doesn't use trunk
 >> anyway) will test it unless it can easy and safely be tested without
 >
 >The solution is simple. Create at least three rc (Release Candidate)
 >releases. This will greatly improve the stability of a final release
 >without the need for many point releases. Everybody in the software
 >world knows that rc release can contain some bugs and will probably be
 >fixed before the final release. But then I guess the argument starts,
 >that releases take to long to create. In the world of software
 >development that could, and should be streamlined, and never be an
 >excuse.
 >
 >
 >-- 
 >Regards,
 >  - Graeme -
 >
 >
 >_______________________________________________
 >fpGUI - a cross-platform Free Pascal GUI toolkit
 >http://opensoft.homeip.net/fpgui/
 >
 >--
 >_______________________________________________
 >Lazarus mailing list
 >Lazarus at lists.lazarus.freepascal.org
 >http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
 > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20100520/053633ea/attachment-0004.html>