Hi all, just polished up the Torque-site module a little bit and with some more code changes (MySQL, PostgresQL and Oracle) the question is, if we may take the effort to finish the release preparation in the next quarter? Do we need some more time?
Hopefully all tests in torque-test succeed? I did successfully torque-trunk: mvn -P apache-release,beans,managers clean install torque-test: mvn -P hsqldb,beans,managers clean test mvn -P mysql,managers,beans clean test mvn -P mysql,docker-testcontainer,managers,beans clean test mvn -P postgresql,docker-testcontainer,managers,beans clean test TODO profile check: oracle (DONE?), mssql Jenkins (builds.apache.prg) does perform (in root) without errors mvn -Ptest,derbyEmbedded-jenkins,beans,managers clean package mvn -Ptest,hsqldb-jenkins,beans,managers clean package mvn clean install cobertura:cobertura findbugs:findbugs checkstyle:checkstyle pmd:pmd pmd:cpd mvn -Powasp -Dtest=false -DfailIfNoTests=false clean verify - ExceptionMapperTest#testTransactionDeadlock does not return and is still skipped for hsqldb (2.5.0), but https://issues.apache.org/jira/browse/TORQUE-356 seems at least partially resolved as I could not find any special handling of ignoreCaseInOrderBy in torque-runtime. - Docker-Testcontainer were extended to use PostgresQL and did help to improve the checks, but not all tests and other databases except MySQL are not included yet .. - a good many issues are resolved, but some work is remaining for future releases, so what? We may do a follow up release v4.1.1 (or 5.0.1), if we discover some (heavy) bugs, but a first dotzero-release (4.1.0/5.0.0) could help a lot to check for the better IMO, upstream integration projects get a signal, that it's time to do some work and checks ... ;-) Sure, it's work to manage a release, but we could divide efforts .. Do we agree to switch to a 5.0.0 release and update JIRA issues/version? Splitting up into two versions does not make sense (going back in time etc., exclude some commits). Have fun! Best regards, Georg Von: "Georg Kallidis" <georg.kalli...@cedis.fu-berlin.de> An: "Apache Torque Developers List" <torque-dev@db.apache.org> Datum: 19.12.2019 11:54 Betreff: Re: Re: Torque 4.1? Hi all, thanks for all the replies! @The question is whether torque-test runs ok or not. Ok, I tested almost only mysql and hsqldb. I will check hsqldb and postgreSQL and hopefully Oracle SQL could be fixed, though MSQ SQL still remains not tested thoroughly .. I did some MySQL SQL generation change recently... Thinking about this, it might be a structural improvement needed, if the project would be in more active mode. I do not think, about splitting up torque structure into database specific submodules, but a solution has to be found about some flexibility in database support. Might be, that not all databases could get the same test level with the current community ... @The issue [TORQUE-356] mainly was about the introduction of timezones into datetime columns" It might be helpful to get some more hints in the issue, what exactly is missing? @Versioning Thomas might be right, and with semantic versioning in mind we might better use v5.0 - although I am not yet aware of breaking dependencies in generated java code, but Java 8 is now required. Summary IMO: It might be necessary to check some more capabilities (databases, ant tasks integration ??), until we could release Torque. Nevertheless I personally would prefer to do it as early as possible. Hopefully the remaining must-have TODOs/issues will boil down very soon to zero! ;-) Best regards, Georg BTW https://db.apache.org/torque/torque-4.0/ site navigation of needs some updates as well, e.g. Wiki should point to https://cwiki.apache.org/confluence/display/DBTORQUE/Home Von: Thomas Vandahl <t...@apache.org> An: Apache Torque Developers List <torque-dev@db.apache.org> Datum: 18.12.2019 20:23 Betreff: Re: Torque 4.1? On 18.12.19 16:59, Georg Kallidis wrote: > today I worked on a couple of TORQUE issues, which blocked the release of > Torque 4.1, but could be resolved (someone checks this?). The question is whether torque-test runs ok or not. I got access to a fairly recent Oracle server and found that the Oracle tests are broken. They already fail because of invalid SQL-files being generated. > Still remaining are TORQUE-355 "Improve support for HSQLDB 2.x" and > TORQUE-356 "Implement millisecond support for MySQL timestamps". > - TORQUE-356 seems to be actually resolved as Hsqldb 3.x is now used - ? There are some instanceof-checks in the tests that exclude several feature tests that HSQLDb now has. I wanted to check whether these exclusions are now obsolete or not. However, the above-mentioned issue mainly was about the introduction of timezones into datetime columns. This broke some tests. > May be to lift the release version from 4.1 to 5.1 for the Torque release > as well? I have to admit that I changed quite a lot and deleted stuff without caring too much for backward compatibility. My guess would be that we are no longer in a 4.x-range but need at least 5.0 Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
smime.p7s
Description: S/MIME Cryptographic Signature
