<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>In my wishlist of waiting PR, we had this one (OGC Filters to WMS
      in QGIS server) : <a class="moz-txt-link-freetext" href="https://github.com/qgis/QGIS/pull/5561">https://github.com/qgis/QGIS/pull/5561</a> :)<br>
    </p>
    <p>Y.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Le 28/11/2017 à 09:42, DelazJ a écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAECJsSpoqo9=DoSyeP_GKOxy9m8ev=6L9Cc-X9keriXikk+V3A@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>Hi,<br>
              </div>
              There's a pull-request i'm missing in the list since the
              beginning: <a
                href="https://github.com/qgis/QGIS/pull/4305"
                moz-do-not-send="true">https://github.com/qgis/QGIS/pull/4305</a><br>
            </div>
            I'm not sure it'd break an API, and it looks like a new
            feature but I think it'd be a shame to not have it for 3.0.
            I don't know if Nathan has time to work on it but this is a
            nice tool to help users migrate from 2.x to 3.0 easily. I'm
            not sure it will get enough sense in 3.2 when a lot of
            people would have already (maybe) struggled to move their
            settings, unless I overestimate the PR scope and there's
            already a migration process I did not find.<br>
            <br>
          </div>
          Regards,<br>
        </div>
        Harrissou<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2017-11-28 3:11 GMT+01:00 Mathieu
          Pellerin <span dir="ltr"><<a
              href="mailto:nirvn.asia@gmail.com" target="_blank"
              moz-do-not-send="true">nirvn.asia@gmail.com</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="auto">+1 to all four PRs, especially the dynamic
              number value for processing one which I've tested quite a
              lot in the last 48 hours and couldn't detect any problem.</div>
            <div class="HOEnZb">
              <div class="h5">
                <div class="gmail_extra"><br>
                  <div class="gmail_quote">On Nov 28, 2017 6:39 AM,
                    "Nyall Dawson" <<a
                      href="mailto:nyall.dawson@gmail.com"
                      target="_blank" moz-do-not-send="true">nyall.dawson@gmail.com</a>>
                    wrote:<br type="attribution">
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">On
                      27 November 2017 at 08:32, Tim Sutton <<a
                        href="mailto:tim@kartoza.com" target="_blank"
                        moz-do-not-send="true">tim@kartoza.com</a>>
                      wrote:<br>
                      > The voting process is transparent but only
                      qgis/QGIS core committers may vote on it. Please
                      note that if you are eligible you should have
                      received an invite email to join the loomio group.
                      If you did not, please contact me with your
                      preferred email address and I will re-add you.<br>
                      ><br>
                      <br>
                      Hi Tim,<br>
                      <br>
                      What's the process to get exemptions for open PRs?
                      There's a couple<br>
                      I'd like to see merged if it's agreeable:<br>
                      <br>
                      - <a
                        href="https://github.com/qgis/QGIS/pull/5600"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://github.com/qgis/QGIS/p<wbr>ull/5600</a>:
                      "Add order by expression<br>
                      processing algorithm". Very low risk - it's a self
                      contained algorithm<br>
                      on which nothing else depends. Processing in 3.0
                      is awesome, and has<br>
                      made great strides to becoming a competitive ETL
                      tool. This algorithm<br>
                      would very nicely complement the work already done
                      in 3.0 to make<br>
                      models more powerful and flexible.<br>
                      <br>
                      - <a
                        href="https://github.com/qgis/QGIS/pull/5430"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://github.com/qgis/QGIS/p<wbr>ull/5430</a>:
                      "More output format choices<br>
                      in raster save as dialog": Low risk. Changes only
                      affect the dialog,<br>
                      and an extra convenience member in
                      QgsRasterFileWriter (which is<br>
                      accompanied by unit tests)<br>
                      <br>
                      - <a
                        href="https://github.com/qgis/QGIS/pull/5729"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://github.com/qgis/QGIS/p<wbr>ull/5729</a>:
                      "[processing] Expose dynamic<br>
                      ("data defined") numeric parameters to gui".
                      Low-medium risk. Most of<br>
                      the changes here are gui related, just exposing
                      functionality which<br>
                      already exists in the new processing backend (and
                      which is covered by<br>
                      stacks of unit tests). I'd love to see this
                      included in 3.0 as it<br>
                      changes some of the processing API, and I would
                      like wider testing and<br>
                      porting of algorithms to utilise this BEFORE the
                      API is locked in<br>
                      place and we're stuck with it. I'd rather identify
                      any issues in the<br>
                      related API here for 3.0. Additionally, the
                      changes to the "set z<br>
                      value" algorithm which allows the z value to be
                      pulled from a field or<br>
                      expression is extremely useful in preparing
                      datasets for use in the<br>
                      new 3d views. Plus, it's an absolute KILLER
                      feature to have.<br>
                      <br>
                      - <a
                        href="https://github.com/qgis/QGIS/pull/5663"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://github.com/qgis/QGIS/p<wbr>ull/5663</a>:
                      "Add a name for transactions<br>
                      created from executeSql". It's marked as a feature
                      and tagged as 3.2,<br>
                      but looking over it it seems to be almost entirely
                      api tweaks and a<br>
                      unit test. I'd say this is low risk, especially
                      given Paul's history<br>
                      of stable commits and how well unit tested this
                      are of code is<br>
                      already.<br>
                      <br>
                      Nyall<br>
                      ______________________________<wbr>_________________<br>
                      Qgis-psc mailing list<br>
                      <a href="mailto:Qgis-psc@lists.osgeo.org"
                        target="_blank" moz-do-not-send="true">Qgis-psc@lists.osgeo.org</a><br>
                      <a
                        href="https://lists.osgeo.org/mailman/listinfo/qgis-psc"
                        rel="noreferrer" target="_blank"
                        moz-do-not-send="true">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-psc</a></blockquote>
                  </div>
                </div>
              </div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            Qgis-psc mailing list<br>
            <a href="mailto:Qgis-psc@lists.osgeo.org"
              moz-do-not-send="true">Qgis-psc@lists.osgeo.org</a><br>
            <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-psc</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Qgis-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-psc">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></pre>
    </blockquote>
    <br>
  </body>
</html>