<div class="gmail_quote">2011/7/29 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Friday 29 July 2011, David Cole wrote:<br>
> Hi all,<br>
><br>
> Replies requested. Short replies only. Read on. Just a short reply with bug<br>
> numbers or links to the bugs is all we need here. Please move specific<br>
> discussions into the bugs themselves or start a new thread to talk about<br>
> it... Replies on this thread should just be a collector for bug numbers.<br>
><br>
> Example one-line reply:<br>
><br>
> <a href="http://public.kitware.com/Bug/view.php?id=8707" target="_blank">http://public.kitware.com/Bug/view.php?id=8707</a><br>
><br>
> We are planning for CMake 2.8.6 already, and it's going to be a compressed<br>
> release cycle this time around. We're targeting Sept. 14, 2011 for<br>
> releasing it, and in order to make that happen we'll have to do an "rc1"<br>
> as early as Aug 10th or 17th... just 2 or 3 weeks from now.<br>
<br>
</div>From the KDE point of view this is somewhat unfortunate, that exactly this<br>
cycle will be shorter.<br>
Are there reasons for it ?<br></blockquote><div><br>There are reasons for it. For one thing, the 2.8.5 release took too long, so we want to make this one shorter to keep us on schedule for getting 4 releases per year out there. If we can actually deliver 2.8.6 on Sept. 14th, we can reliably plan on 2.8.7 being delivered in mid-December.<br>
<br>It may be unfortunate, but we will stick with it unless we receive mucho objections from others in addition to KDE.<br><br>Is mid-December too far in the future? (And a minimum version of 2.8.7...?)<br><br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
With the coming Qt5 and the binary break this causes in KDE we plan to also<br>
break binary compatibility once (while keeping source compatibility similar to<br>
Qt more or less completely).<br></blockquote><div><br>When is the Qt5 release scheduled for?<br><br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
With this break we will also use the chance to break our cmake source<br>
compatiblity once, the first time since KDE 4.0.0 in early 2007.<br>
Which means we try to merge a lot of our stuff into cmake, and then depend on<br>
this version of cmake, i.e. 2.8.6.<br>
2.8.7 will be released maybe around January or so, right ? This would be quite<br>
late for us.<br>
This does not just mean merge, but also change it so it becomes acceptable for<br>
cmake, etc.<br>
<br>
This is the list of files in KDE which are potential candidates for being<br>
upstreamed:<br>
<a href="http://community.kde.org/index.php?title=KDE_Core/Platform_11/Buildsystem/FindFilesSurvey" target="_blank">http://community.kde.org/index.php?title=KDE_Core/Platform_11/Buildsystem/FindFilesSurvey</a><br>
<br>
Not all files listed on this page have realistic chances IMO.<br>
But I'd really like to get rid of the copies in KDE of the files in the<br>
sections "2 Check*.cmake files", "3 Generic Macros" and "5.1.1 Find*.cmake<br>
from kdelibs which exist in cmake".<br>
<br>
If you look there, already in these three sections there are still a lot of<br>
files marked as TODO.<br>
Getting all that done until August 10th is hard, to say the least. Also now is<br>
the time for summer vacations, which makes it even more hard.<br>
<br>
So, from our (KDE) side being able to work on the stuff listed on the page<br>
linked above until like end of September would be ideal.<br>
(additionally there are the things like automoc which I already started<br>
discussing on the cmake developers list).<br>
<br>
Alex<br>
<br>
</blockquote></div><br>That is an ambitious amount of work. I'm skeptical that we could even fit all that into a mid-September rc1, let alone a mid-August rc1... It would probably be better if you shoot for getting that in by November, and counting on a December release of CMake 2.8.7.<br>
<br>Let me know if you have further thoughts or comments here.<br><br>Thanks,<br>David<br><br><br>