<br><br><div class="gmail_quote">On Sun, Mar 25, 2012 at 8:50 PM, <span dir="ltr"><<a href="mailto:f-myth-users@media.mit.edu">f-myth-users@media.mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've been pondering this for a couple weeks, ever since I saw Mike's<br>
commit of 2012-03-09T15:20:56-08:00 and his message re "Upgrad failing<br>
from schema 1214 to 1265)" [sic]. This is a new thread 'cause I'm not<br>
sure if very late replies to old threads typically get seen. Sorry if<br>
this is a bit long, but thanks for whatever you can clarify.<br>
<br>
I understand the problem with supporting old Myth versions if their<br>
surroundings also change, but can you be a little clearer on a few<br>
issues here? And I'm hoping to perhaps change your mind, or at least<br>
get workable ways forward---maybe support old versions until 0.25 is<br>
released and -then- drop them, with more warning than the zero that<br>
such users got before your commit?<br></blockquote><div><br></div><div>Cutting the below, can't you just upgrade to 0.23, 0.24, then 0.25 in order using the tarballs? I've seen that before in plenty of commercial products and should work just fine here was well.</div>
<div><br></div><div>Kevin</div></div>