<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Sugar activities from the beginning identified versions by version
    number. For some activities we have tens of versions in ASLO.
    Switching version control from a version number to git branches may
    be non-trivial. It would certainly be helpful to view changes to
    activities over time. <br>
    <br>
    I still believe it is far more important to have a link from the
    ASLO entry for an activity to its github repo than to include the
    link in activity.info.<br>
    <br>
    Tony<br>
    <br>
    <div class="moz-cite-prefix">On 05/17/2016 07:37 PM, Walter Bender
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADf7C8sSe4VU2dvuVqv+u2KxD3M7PsPN4NFr0Ge6VUBC7ghVzA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, May 17, 2016 at 12:35 PM,
            Dave Crossland <span dir="ltr"><<a
                moz-do-not-send="true" href="mailto:dave@lab6.com"
                target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:dave@lab6.com">dave@lab6.com</a></a>></span> wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div dir="ltr">
                <div class="gmail_extra"><span class=""><br>
                    <div class="gmail_quote">On 17 May 2016 at 09:46,
                      Walter Bender <span dir="ltr"><<a
                          moz-do-not-send="true"
                          href="mailto:walter.bender@gmail.com"
                          target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a></a>></span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">we
                        need to send out a clear description of what is
                        expected of App developers ("transfer" their
                        repos to sugarlabs) and how to manage issues
                        once the switch-over has occurred.</blockquote>
                    </div>
                    <br>
                  </span><a moz-do-not-send="true"
href="https://wiki.sugarlabs.org/go/Infrastructure_Team/Migrating_Bugs_to_GitHub"
                    target="_blank">https://wiki.sugarlabs.org/go/Infrastructure_Team/Migrating_Bugs_to_GitHub</a></div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Great. Thx.</div>
            <div> </div>
          </div>
          <br>
          <br clear="all">
          <div><br>
          </div>
          -- <br>
          <div class="gmail_signature">
            <div dir="ltr">
              <div><font><font>Walter Bender</font></font><br>
                <font><font>Sugar Labs</font></font></div>
              <div><font><a moz-do-not-send="true"
                    href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
                <br>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>