[10:01]<simono> we (not sure who) need to make jala 1.4 [10:02]<simono> jala trunk is not very fresh and mainly missing the unittest changes [10:02]<simono> ^^ talking about 1.3, not trunk [13:22]<hannesw> simono: i was using jala trunk for helma 1.7 originally [13:22]<hannesw> but the unit tests rely on the jala 1.3 behaviour [13:22]<hannesw> (setup and cleanup only called once per test file) [13:22]<hannesw> and i didn't want to update that now [13:23]<hannesw> but yes, a new jala release would be great! [13:27]<simono> okay maybe we can fix helma-tests to work with jala trunk [13:27]<simono> trunk has roberts database-switching stuff which is really nice ... and other minor improvements [13:33]<simono> you mean those tests .. i can adapt them next days if you want SVN//apps/modules/trunk/test/tests [13:37]<simono> we have jala-trunk in production so hopefully its stable :) [14:00]<hannesw> great, thanks! [14:00]<hannesw> but beware, it might be more work than you think. [14:01]<hannesw> yippie, just implemented (optional) markdown formatting on helma.org [14:01]<hannesw> http://dev.helma.org/wiki/Markdown+Formatting/ [14:59]<simono> ok, more work then i thaugt.. gonna talk it over with robert [15:00]<simono> for those selftests it's probably a bad idea to use the ram-db instead of real-thing. this is what most of our code does: setup makes fresh db, cleanup throws it away [15:08]<earl> hannesw_: markdown, yay! [15:09]<hannesw_> :)