Hello David.<br><br>That's the best option in my opinion.<br><br><br>cheers!.<br clear="all">Rafael Ortiz <br>
<br><br><div class="gmail_quote">On Thu, Jun 18, 2009 at 11:31 AM, David Farning <span dir="ltr"><<a href="mailto:dfarning@sugarlabs.org">dfarning@sugarlabs.org</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;">
Chris,<br>
<br>
Upon further examining<br>
<a href="http://wiki.laptop.org/go/Activities/Browse_%288.2%29" target="_blank">http://wiki.laptop.org/go/Activities/Browse_(8.2)</a>, I think that we can<br>
maintain backwards compatibility both technically and socially by<br>
using the existing /Activities/NAME_(VERSION) by pointing the links on<br>
that page to<br>
<br>
<a href="http://activities.sugarlabs.org/sugar/addon/4024" target="_blank">http://activities.sugarlabs.org/sugar/addon/4024</a><br>
and<br>
<a href="http://activities.sugarlabs.org/sugar/downloads/latest/4024/" target="_blank">http://activities.sugarlabs.org/sugar/downloads/latest/4024/</a><br>
<br>
This would not require any changes on currently deployed machines,<br>
just server side url updates. I need to double check that the version<br>
detection happens correctly.<br>
<br>
Does this sound reasonable for a transition period?<br>
<br>
david<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div><br>