<div class="gmail_quote">On Mon, May 18, 2009 at 3:15 PM, Jonathan Marsden <span dir="ltr"><<a href="mailto:jmarsden@fastmail.fm">jmarsden@fastmail.fm</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Ben Morgan wrote:<br>
<br>
> I wonder if we need to release some of the important utilities at<br>
> different times from the engine. (i.e. have a osis2mod release once<br>
> problems are fixed with it)<br>
<br>
</div>To me, this suggests more the need for (more and better?) automated<br>
tests of the utilities, rather than a different release schedule for<br>
them? As you fixed the issues you found, did you add to the test suite<br>
regression tests for them? If not, is there something in the overall<br>
testing structure that makes that difficult or impractical to do?<br>
</blockquote><div>I didn't add regression tests... I'm not sure how workable they are. (though they would probably be a good idea)<br>There are two ways you could attack the problem:<br>Either you store input and expected output for lots of different test cases - but a reasonable component of these will be binary and as such not really allow easy comparing. <br>
The other option would be to generate a lot of modules and then fetch verses from them, I suppose.<br>It would mean that every time you changed the output (this happened with more than one thing in 1.6.0), you would have to change potentially a large number of expected outputs.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
If we are now to enjoy rapid (every month or two?) 1.6.x update<br>
releases, then I'm not sure there would be much benefit to doing utility<br>
releases in between those, would there? And you'd need a different<br>
version numbering scheme, and a separate source tarball... <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I'd rather we just aim for more frequent SWORD releases :)</blockquote><div>These are (as far as I can see) critical issues and need (relatively) immediate fixing.<br>People have complained before about being expected to run SVN osis2mod to get the latest version... <br>
<br>In some ways osis2mod changes are important to be released quickly. <br>Since most osis2mod changes probably don't require a new engine version, we are supporting a range of previous versions (though this isn't true in 1.6.0). If we have improved osis2mod support, we should release it ASAP to stop bad module creation happening - there are few things worse than having badly formatted modules around.<br>
</div></div><br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br>
in the valley of decision.<br><br>Giôên 3:14 (ESV)