<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">Another thought which might be nice...
      How about possibly a documentation day (or partial day)?  This
      could be for supporting many forms of documentation (blogs, user
      docs, manpages (if any needed), screencasts...).<br>
      <br>
      Brad<br>
      <br>
      On 12/06/2012 02:04 PM, Eric D Helms wrote:<br>
    </div>
    <blockquote
cite="mid:CAFWK8FLCogKsAXyP59qY8DwgoGhovk3FxsoE13vpxtr2nX+6iA@mail.gmail.com"
      type="cite">I think this would be a great time for a bug-day and
      am going to organize such.  Bug day being, whole team sitting down
      and pounding through the list of bugs to verify, ask for more
      information or try and fix.  I figure we can get a conference room
      for a day (in the U.S.) to allow easy discussion since inevitably
      some people have more information than others in some areas.
      <div>
        <br>
      </div>
      <div>Team Other side of the Pond -- since the time zone difference
        is great enough, if you guys would also like to put together a
        bug day around the same time and if someone from your side would
        like to volunteer the organization of it that would be great.</div>
      <div><br>
      </div>
      <div>- Eric</div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, Dec 6, 2012 at 12:47 PM, Tom
          McKay <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:thomasmckay@redhat.com" target="_blank">thomasmckay@redhat.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class="im"><br>
              <br>
              ----- Original Message -----<br>
              > From: "Eric D Helms" <<a moz-do-not-send="true"
                href="mailto:ericdhelms@gmail.com">ericdhelms@gmail.com</a>><br>
              > To: <a moz-do-not-send="true"
                href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a><br>
              > Sent: Thursday, December 6, 2012 11:58:28 AM<br>
              > Subject: [katello-devel] Katello 1.3/1.4 Feature
              Planning<br>
              ><br>
              ><br>
            </div>
            <div>
              <div class="h5">> Howdy,<br>
                ><br>
                ><br>
                > As I prepare the Katello 1.2 release, I thought I
                would get the ball<br>
                > rolling on feature planning for Katello 1.3. As it
                stands, the focus<br>
                > of Katello 1.3 is Pulp V2 integration. However, a
                lot of other<br>
                > features and work will go on during now and when
                the Pulp V2 work is<br>
                > ready. So I'd like to get a rough idea of what
                features we plan to<br>
                > try and get into this next release and potentially
                any beyond that<br>
                > for the next release nanny to work from. Current
                rough time frame<br>
                > for Pulp V2 integration is late January, early
                February time frame<br>
                > and thus this release will be based on feature
                completion not a hard<br>
                > timed release.<br>
                ><br>
                ><br>
                > Katello 1.3 Features<br>
                > - Pulp V2 integration<br>
                > - Pulp V2 upgrades<br>
                ><br>
                ><br>
                ><br>
                ><br>
                > Katello 1.4 Features<br>
              </div>
            </div>
            <div class="im">>
              _______________________________________________<br>
              > katello-devel mailing list<br>
              > <a moz-do-not-send="true"
                href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a><br>
              > <a moz-do-not-send="true"
                href="https://www.redhat.com/mailman/listinfo/katello-devel"
                target="_blank">https://www.redhat.com/mailman/listinfo/katello-devel</a><br>
              <br>
              <br>
            </div>
            Reduction of the 564 open BZs. Seriously, if we're not going
            to fix them let's just mass close.<br>
            <br>
            <a moz-do-not-send="true"
href="https://bugzilla.redhat.com/buglist.cgi?quicksearch=NEW%2CASSIGNED%20product%3A%22katello%22%2C%22CloudForms%20System%20Engine%22%2C%22Subscription%20Asset%20Manager%22&list_id=912048"
              target="_blank">https://bugzilla.redhat.com/buglist.cgi?quicksearch=NEW%2CASSIGNED%20product%3A%22katello%22%2C%22CloudForms%20System%20Engine%22%2C%22Subscription%20Asset%20Manager%22&list_id=912048</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
katello-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a></pre>
    </blockquote>
    <br>
  </body>
</html>