Looking for compiler testers.
Posted: 09.06.2006, 13:58
Hi all,
I'm looking for some people who want to do some small testing job.
I'm currently applying user patches, bugfixes, ... from you to Testing branch of the SVN repository.
I test if these modifications compile on D5, D7 and D2006. I also check if the testsuite isn't broken in D7 for Mysql database.
If packages have to be modified I try to do so for these compilers as well.
However... sometimes we hear there's a package broken for Lazarus, BCB, D6, D2005.
Who wants to commit himself to this job for the compilers I can't check?
What does it involve? Say, twice a mont you should:
- update you SVN copy from svn testing branch
- rebuild all packages
- if testing suite is (or can be made) available for your platform run the testing suite to see if more error show up than before.
- if possible, compile one of your testing programs with the new version to see if you can still connect to the database of your choice.
- if you can, send a patch to fix eventual problems that are compiler specific. (mainly package files, I think)
I hope you respond well so I can fill out the gaps in following list. Even if somebody else also volunteered, you're welcome to reply to this call.
D5 : mdaems
D6 : zippo
D7 : mdaems, muthuhk, noelc, artur, aperger
D8 :
D2005 : aperger
D2006 : mdaems, zippo, muthuhk, noelc
Lazarus : barko, fbaqui
BCB5 :
BCB6 :
Kylix 3 :aperger
mysql 3.x : zippo
mysql 4.0 : artur
mysql 4.1 : artur
mysql 5 : zippo, mdaems
postgresql : aperger
postgresql 7.x : muthuhk
postgresql 8.x : muthuhk, noelc
MSSQL :aperger
MSSQL2000 : noelc
MSSQL2005 : noelc
Firebird : aperger
Firebird 2 : noelc
...
Thanks a lot!!
Mark
BTW, please, do not respond to this thread for 'non yes' answers to keep it manageable. If you have comments, please open a new thread.
I'm looking for some people who want to do some small testing job.
I'm currently applying user patches, bugfixes, ... from you to Testing branch of the SVN repository.
I test if these modifications compile on D5, D7 and D2006. I also check if the testsuite isn't broken in D7 for Mysql database.
If packages have to be modified I try to do so for these compilers as well.
However... sometimes we hear there's a package broken for Lazarus, BCB, D6, D2005.
Who wants to commit himself to this job for the compilers I can't check?
What does it involve? Say, twice a mont you should:
- update you SVN copy from svn testing branch
- rebuild all packages
- if testing suite is (or can be made) available for your platform run the testing suite to see if more error show up than before.
- if possible, compile one of your testing programs with the new version to see if you can still connect to the database of your choice.
- if you can, send a patch to fix eventual problems that are compiler specific. (mainly package files, I think)
I hope you respond well so I can fill out the gaps in following list. Even if somebody else also volunteered, you're welcome to reply to this call.
D5 : mdaems
D6 : zippo
D7 : mdaems, muthuhk, noelc, artur, aperger
D8 :
D2005 : aperger
D2006 : mdaems, zippo, muthuhk, noelc
Lazarus : barko, fbaqui
BCB5 :
BCB6 :
Kylix 3 :aperger
mysql 3.x : zippo
mysql 4.0 : artur
mysql 4.1 : artur
mysql 5 : zippo, mdaems
postgresql : aperger
postgresql 7.x : muthuhk
postgresql 8.x : muthuhk, noelc
MSSQL :aperger
MSSQL2000 : noelc
MSSQL2005 : noelc
Firebird : aperger
Firebird 2 : noelc
...
Thanks a lot!!
Mark
BTW, please, do not respond to this thread for 'non yes' answers to keep it manageable. If you have comments, please open a new thread.