I'm not sure if others are as confused as me, but for someone with substantial sized collections in PLaneT that wants a smooth migration to V4 without breaking V3.72 it isn't 'obvious' how to do this in the context of PLaneT.  Should we use the new languages (like scheme or scheme/base or scheme/gui)?  If we do so, will we break our packages in V3.72 (which is definitely not a good thing to do)?  Should we continue to use the mzscheme language until the transition is complete?  Should we maintain two version of our collections - one for V3.72 (distributed via PLaneT) and another for V4 (distributed by some other mechanism)?  I'm already having to maintain separate documentation mechanisms across the two as we go to Scribble and I haven't seen how we're going to smoothly merge these across the V3 -> V4 boundary.  This is probably enough of a list for now.<br> <br>Doug<br><br><div class="gmail_quote">On Wed, Jan 30, 2008 at 2:40 PM, Robby Findler <<a href="mailto:robby@cs.uchicago.edu">robby@cs.uchicago.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Sorry for not writing this in my first reply.<br> <div class="Ih2E3d"><br> On Jan 30, 2008 2:34 PM, Doug Williams <<a href="mailto:m.douglas.williams@gmail.com">m.douglas.williams@gmail.com</a>> wrote:<br> </div><div class="Ih2E3d">> What other constructs might bite us?<br> <br> </div>See plt/doc/release-notes/mzscheme/MzScheme_4.txt.<br> <br> hth,<br> <font color="#888888">Robby<br> </font></blockquote></div><br>