<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 08/29/2013 05:35 AM, Thomas Gilliard
      wrote:<br>
    </div>
    <blockquote cite="mid:521F4016.4000704@gmail.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">On 08/28/2013 11:03 AM, Gonzalo
        Odiard wrote:<br>
      </div>
      <blockquote
cite="mid:CAJ+iPVQk6e6Kg5Fi=B=TTK-C8ohKyttxZ1Gr_Go+hoqWfwzXtA@mail.gmail.com"
        type="cite">
        <div dir="ltr">I agree in the need of testing.
          <div>Testing is more difficult this cycle because:</div>
          <div>* We have less developers working.</div>
          <div>* We don't have the images we usually used to test on our
            main hardware platform (XO*) yet.</div>
          <div>I don't know if any test is done now on Fedora 20 Sugar
            spin,</div>
        </div>
      </blockquote>
      Soas F20 Alpha TC1 live x86_64 starts as a gnome desktop with only
      e-toys and a utility group of apps. There is no sugar.<br>
      yum install @sugar-desktop does not install sugar.  This has been
      the case for a while in nightly composes also.<br>
      <br>
      TC2 is just out and I am looking at it.<br>
    </blockquote>
    <br>
    Same for f20 Alpha TC2:<br>
    <a class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/File:Soas-Alpha-TC2-x86_64.png">http://wiki.sugarlabs.org/go/File:Soas-Alpha-TC2-x86_64.png</a><br>
    <blockquote cite="mid:521F4016.4000704@gmail.com" type="cite"> <br>
      Tom Gilliard<br>
      <blockquote
cite="mid:CAJ+iPVQk6e6Kg5Fi=B=TTK-C8ohKyttxZ1Gr_Go+hoqWfwzXtA@mail.gmail.com"
        type="cite">
        <div dir="ltr">
          <div>but according to Peter Robinson mail, not too much
            communication from that part.</div>
          <div>From my part, I am building rpms for Australia, to use
            sugar 0.100 on a F18 image.</div>
          <div>We will do testing on that, but not in the web part, at
            least not now, due to missing dependencies.</div>
          <div><br>
          </div>
          <div>Gonzalo</div>
        </div>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Wed, Aug 28, 2013 at 2:43 PM,
            Daniel Narvaez <span dir="ltr"><<a
                moz-do-not-send="true" href="mailto:dwnarvaez@gmail.com"
                target="_blank">dwnarvaez@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">
                <div class="im">On 28 August 2013 19:33, Walter Bender <span
                    dir="ltr"><<a moz-do-not-send="true"
                      href="mailto:walter.bender@gmail.com"
                      target="_blank">walter.bender@gmail.com</a>></span>
                  wrote:<br>
                </div>
                <div class="gmail_extra">
                  <div class="gmail_quote">
                    <div class="im">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex"><br>
                        To me the issue is that we have no sense of the
                        urgency of the 250<br>
                        bugs that have not been triaged. Most of the
                        bugs that have been<br>
                        triaged are not urgent and should not hold up
                        the release. (They can<br>
                        be tagged for 102 with little consequence.) But
                        the great unknown is<br>
                        what scares me.</blockquote>
                      <div><br>
                      </div>
                    </div>
                    <div>There are those and there are the N bugs which
                      has not been discovered because people are not
                      testing... We can block rescheduling on completing
                      the triage but can we block on someone doing the
                      testing? This is totally a subjective feeling but
                      my impression is that the worst bugs are
                      unreported.<br>
                      <br>
                    </div>
                    <div>I was hoping to go towards continuous
                      development gradually after 0.100 but now I sort
                      of feel forced into it because there are too many
                      unknowns to put down a schedule.<br>
                    </div>
                  </div>
                </div>
              </div>
              <br>
              _______________________________________________<br>
              Sugar-devel mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
              <a moz-do-not-send="true"
                href="http://lists.sugarlabs.org/listinfo/sugar-devel"
                target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>