From: Arlindo da S. <da...@al...> - 2009-09-29 14:22:35
|
All, After a very busy summer/early fall, I have been able to make a 2.0.a7 build with the opengrads extensions. Although there no new extensions being released (I have a couple in the works but not ready for prime time yet), there have been some improvements under hood. Most importantly, I have added a detailed unit test suite for the extensions. Here is the build sequence after your untar: % ./configure % make % make check (to test the core grads engine) % make gex-check (to test the extensions) % make bundle-dist (to create tarballs for sf.net) There a total of 75 new tests for the extensions. Some of these will say "skipped", which means that these a place holders (a real test is yet to be written). These tests are very important to make sure changes in the main engine by COLA do not break the extensions. Mike: all the tests in libmf are place holders; just enter the test code under mf/ut.py (use the other */ut.py as examples). We also need documentation... Jennifer: I usually ship a full set of HTML documentation with the bundle for those cases when you are offline and need to look something up. Lately the doc/ directory in your tarballs have not been updated. Do you think you could update this for "a8"? BTW, I never released a 2.0.a6. Mike reported that it had broken his wxmap system and we suspected the extensions were hosed. This prompt me to write these tests, and it took me longer than anticipated. Let me know if you experience any problem with the build. Cheers! Arlindo -- Arlindo da Silva da...@al... |