<div dir="ltr">It sounds right<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/2 Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've come to the conclusion that having a whole swathe of<br>
ReleaseBuilders is wrong. Mostly this comes down to:<br>
* there is no way of knowing (without a lot of testing) that your<br>
ReleaseBuilderForSpecialCircumstances still works after that trivial<br>
refactoring you just did to ReleaseBuilder, and just as importantly,<br>
* who would want to make a 4.4 release (or 4.3, or 3.11, or 3.10!)<br>
from a 4.5 image?<br>
<br>
There's a slight argument in the case of ReleaseBuilderNihongo and<br>
ReleaseBuilderSqueakland, but I'd argue that these too don't belong in<br>
_trunk_.<br>
<br>
So I would like to turn ReleaseBuilderFor4dot5 into the one and only<br>
ReleaseBuilder, delete the old 3.11-4.4 builders, and put<br>
ReleaseBuilder(Nihongo|Squeakland) into a separate package, loaded in<br>
during the release process but otherwise not in Trunk. (In other<br>
words, they go the same route as XML-Parser, Universes and so on.)<br>
<br>
Thoughts? Comments?<br>
<span class="HOEnZb"><font color="#888888"><br>
frank<br>
<br>
</font></span></blockquote></div><br></div>