[fpc-devel] Breaking change in FPC 2.6.1

Jonas Maebe jonas.maebe at elis.ugent.be
Wed Apr 25 13:10:10 CEST 2012

Graeme Geldenhuys wrote on Wed, 25 Apr 2012:

> On 25 April 2012 11:08, Ludo Brands <ludo.brands at free.fr> wrote:
>> I understand. Just wanted to clarify that, to my knowledge, all 3rd party
>> dataset descendants and some other programs using bookmarks are affected by
>> a change that wanted to minimize compatibility problems.
> Indeed, and it now has the total opposite effect.
> Shouldn't such code breaking changes be left to Trunk (2.7.1) and new
> major FPC releases only. As far as I know, 2.6.x is now a "fixes"
> branch which should only allow _bug fix_ commits - nothing more!

That's not entirely correct. It's of course mainly for fixes, but  
small new features or important bug fixes that may break backwards  
compatibility can also be merged under certain circumstances. What is  
acceptable and what is not is obviously in the eye of the beholder,  
and it's not uncommon to also have internal discussions about that  
among the core developers.

> [Marco: practice what you preach]

If your intention is to get this resolved to your satisfaction, then  
making it personal probably also has the "total opposite effect".


More information about the fpc-devel mailing list