The current focus is all on whether the engine can be recompiled in different platforms, each with its own idiosyncrasies. That's natural at this stage. Most of the developers are responding in like manner.
I''m rather more concerned with module development, and how this fares after the software release. Unless the testing phase of the release candidate includes checking whether a module built with the SWORD utility (e.g. osis2mod) from the same software build, and is then tested as a module in a front-end that has been recompiled with the release candidate of the SWORD engine, how can anyone be confident that the software is ready to be released? And how many features does such a module need to have to create such confidence? Does anyone disagree with this as being a sensible requirement? Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Testing-SWORD-1-7-0RC-tp4652997.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page