Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2013-10

"New" database components in Lazarus 1.0.x

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Reinier Olislagers

Hi,

I'm wondering what the policy is regarding adding components corresponding to code in stable FPC.

See bug
http://bugs.freepascal.org/view.php?id=25167
that Laco, an FPC DB dev, raised.

IIRC, in the past we had similar situation with the mssqlconn (MS SQL Server and Sybase ASE db connectors), and 64 bit database connectors (Oracle, sqlite, I think PostgreSQL) being enabled in Lazarus. However, sorry, I can't remember whether this was in -fixes releases or in e.g. 1.0.

Juha indicated introducing new components in fixes versions is not acceptable:
http://forum.lazarus.freepascal.org/index.php/topic,21693.msg127294.html#msg127294 "Generally new features are not backported. Only bug fixes are. Please use trunk if you need a feature which is only in trunk."

However, I think it would be a shame to not have this functionality in Lazarus as the FPC code is of sufficient quality to be moved to stable, Laz trunk versions have been running with this for a long time (I think more than a year for e.g. the Firebird event monitor), and the components themselves are simple wrappers for the underlying FPC code.

Regardless, it would be nice to have this info and address the bug report in question....

Thanks,
Reinier

Reply by email

Juha Manninen
to Reinier Olislagers
Reinier Olislagers wrote
"Generally new features are not backported. Only bug fixes are. Please use trunk if you need a feature which is only in trunk."

Yes, it is a general rule but I believe exceptions can be made. Is it worth the effort before Lazarus 1.2 comes, I am not sure. Anyway, I have nothing against it.

Juha

Reply by email

Flávio Etrusco
to Juha Manninen
Juha Manninen wrote 12 lines
On Wed, Oct 9, 2013 at 11:00 AM, Reinier Olislagers wrote: > "Generally new features are not backported. Only bug fixes are. > Please use trunk if you need a feature which is only in trunk." Yes, it is a general rule but I believe exceptions can be made. Is it worth the effort before Lazarus 1.2 comes, I am not sure. Anyway, I have nothing against it. Juha --

I would argue that only new features in existing components/code should be avoided in stable branches; there shouldn't be a rule against adding new components, per se. I think of it as analogous to new drivers in Linux, that are allowed basically at any time in the release process...

-Fl?vio

Reply by email

Reinier Olislagers
to Flávio Etrusco
Fl?vio Etrusco wrote 21 lines
On Wed, Oct 9, 2013 at 5:12 AM, Juha Manninen wrote: > On Wed, Oct 9, 2013 at 11:00 AM, Reinier Olislagers > wrote: >> "Generally new features are not backported. Only bug fixes are. >> Please use trunk if you need a feature which is only in trunk." > > Yes, it is a general rule but I believe exceptions can be made. > Is it worth the effort before Lazarus 1.2 comes, I am not sure. > Anyway, I have nothing against it. > > Juha > > -- I would argue that only new features in existing components/code should be avoided in stable branches; there shouldn't be a rule against adding new components, per se. I think of it as analogous to new drivers in Linux, that are allowed basically at any time in the release process... -Fl?vio

Thanks, guys.
I noticed somebody (Mattias?) committed the patch and added them to http://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch Thanks a lot!

Reply by email