<div dir="ltr"><div><br></div>Hi Jürgen,<br><br><div><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 20, 2014 at 11:37 AM, Jürgen E. <span dir="ltr"><<a href="mailto:jef@norbit.de" target="_blank">jef@norbit.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Larry,<br>
<br>
On Thu, 20. Feb 2014 at 09:45:42 -0700, Larry Shaffer wrote:<br>
> I'm definitely in favor of a set release schedule. Though I've missed much of<br>
> the 2.1 development cycle, I feel an obligation to finish fixing some of the<br>
> more serious labeling bugs. Towards this goal, I'd like to work through<br>
> Sunday on those issues, if it is OK to do so.<br>
<br>
If we release last minute on Friday - and I should really have set a exact time<br>
and zone beforehand - at say Anchorage time, we still have about 1 day,<br>
14hrs[1] to work on 2.1 before it is branch 2.2.<br></blockquote><div><br></div><div>Seems appropriate to freeze at the end of Gary's time zone. :-)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Although that will be 10am on Saturday for me - so at least 10hrs of precious<br>
packaging time gone ;)<br>
<br>
But to quote Tim: "We're not going anywhere". There will still be bugs in QGIS<br>
2.3 to work on after the release. And I trust that you're not going to stop<br>
bug fixing just because the fixes don't make it into 2.2.<br></blockquote><div><br></div><div>I'll just do what I can today and tomorrow. I'll keep working on bugs (of course :-). If someone takes up maintaining a 2.2.1 bug fix release branch, I'll backport any of my post-2.2-release bug fix commits. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Of course that's a bit odd and it's an relative arbitrarily set date (and time<br>
and zone) - but I'd still like to keep it.<br>
<br>
> With the new local unit test server classes, I feel pretty confident now that<br>
> any unit tests I make, to ensure the labeling bugs are fixed, should be valid<br>
> across all outputs. But, I have now run out of time.<br>
<br>
Good job. Although we now need lighttp and spawn-cgi now, don't we? I saw<br>
something in the cdash logs. Probably something I need to add to osgeo4w.<br></blockquote><div> <br></div><div>Yes, please do add those to osgeo4w, if possible. QgsLocalServer can be config'd to work with the osgeo4w Apache and some FCGI spawning utility (or as an Apache-spawned FCGI), but I think Apache is a bit too much of a resource hog just to run a local QGIS Server with single connection, e.g. for unit tests or local previewing.<br>
<br></div><div>We discussed before adding lighttpd/spawn-fcgi to the QGIS src build, but opted for external dependencies, which is what I built the new QgsLocalServer around. If the local QGIS Server Preview plugin gets finished [0, mockup], and is considered for core adoption, maybe an internal build would be nice. The latest versions of lighttpd/spawn-cgi have CMake build setups [1,2].<br>
<br></div><div>Also, I didn't have time, but want to add a FindLocalServer.cmake module, which would define:<br><br></div><div>* LOCALSERVER_FOUND<br></div><div>* WEBSERVER_EXECUTABLE<br></div><div>* FCGISPAWN_EXECUTABLE<br>
<br></div><div>That module would be run if ENABLE_TESTS=ON and would look for pairs of web/fcgi-spawn executables that are known to work well together. To pass the found executable paths to the Python test modules, two SET(ENV{QGIS_*_EXECUTABLE}) could be added in UsePythonTest.cmake, or the paths can be written to a file, like is done with qgisbuildpath.txt. Then, QgsLocalServer class could just be set up to look for either.<br>
</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> If I could work from now through Sunday, it would be very productive towards<br>
> labeling fixes for this release. If not, I understand and will do what I can<br>
> today and tomorrow to wrap things up and commit what's working. I will<br>
> endeavor to avoid such extension requests in the future.<br>
<br>
So we need to coordinate that I don't branch between two of your possibly<br>
dependant last minute commits? The interruption by branching should be short.<br></blockquote><div><br></div><div>Ok. I'll try not to commit at the last second. :-) Helpful countdown clock. Thanks.<br><br><br>[0] <a href="https://www.dropbox.com/sh/ymqp2l1prz63iim/15RN8shVF3">https://www.dropbox.com/sh/ymqp2l1prz63iim/15RN8shVF3</a><br>
[1] <a href="http://redmine.lighttpd.net/projects/lighttpd/repository/show/trunk">http://redmine.lighttpd.net/projects/lighttpd/repository/show/trunk</a><br>[2] <a href="http://redmine.lighttpd.net/projects/spawn-fcgi/repository/show/trunk">http://redmine.lighttpd.net/projects/spawn-fcgi/repository/show/trunk</a><br>
<br></div><div>Regards,<br><br></div><div>Larry<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Jürgen<br>
<br>
[1] <a href="http://www.timeanddate.com/countdown/generic?iso=20140221T235900&p0=18&msg=QGIS+2.2+Release" target="_blank">http://www.timeanddate.com/countdown/generic?iso=20140221T235900&p0=18&msg=QGIS+2.2+Release</a><br>
<span class=""><font color="#888888"><br>
--<br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br>
Software Engineer D-26506 Norden <a href="http://www.norbit.de" target="_blank">http://www.norbit.de</a><br>
QGIS PSC member (RM) Germany IRC: jef on FreeNode<br>
<br>
--<br>
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH<br>
Rheinstrasse 13, 26506 Norden<br>
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502<br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</font></span></blockquote></div><br></div></div></div>