<div dir="ltr"><br><div class="gmail_quote"><br><div dir="ltr"><br><div class="gmail_quote"><div class="Ih2E3d"><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 like to pose an alternative goal, inspired by your comment: Glucose<br>
should never attempt to parse version strings. I believe that we can<br>
accomplish this without sacrificing any of the user-facing behaviors that<br>
we truly desire. The choice of an appropriate versioning scheme may then<br>
be left to the author.<br>
</blockquote></div><div><br>I disagree. It is desirable for Sugar to be able to compare versions and guess which one is newer. If, as is the current plan, multiple versions of an activity can coexist on an XO, it is reasonable to want sugar to present these in some sane order, and possibly give hints and/or aid if the user wants to update and/or garbage collect. Otherwise, we might as well just be using activity hash, which can be calculated without being explicitly included in <a href="http://activity.info">activity.info</a>.<br>
</div></div><br></div>
</div><br></div>