[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: New Feature for kdelibs (Was: The case for a kdelibs 4.8)
From: andrea diamantini <adjam7 () gmail ! com>
Date: 2011-11-10 15:54:33
Message-ID: CAH-ukQTQRBTfx8EWNzsmYLVm1rgypQncK9qEaGjAWz53xS3YEA () mail ! gmail ! com
[Download RAW message or body]
2011/11/10 Aaron J. Seigo <aseigo@kde.org>
> On Wednesday, November 9, 2011 23:44:21 Andrea Diamantini wrote:
> > 4.x is where I'm living/fighting/coding/writing now.
>
> for apps and workspaces, that is perfect. we don't want to disrupt app and
> workspace development while we get kdelibs prepped for the next major
> release.
>
> > I'm sorry to say, in my mind next version of kdelibs is 4.8.
>
> your mind is wrong. whatever the version number might end up saying
> (probably
> to keep packagers and users from confusion) it'll be the 4.7 code base with
> continued bug fixes applied :)
>
> > And it will be based on the upcoming (not yet released) Qt 4.8.
>
> sure; but this is a non-relevant detail.
>
> > Thinking about "frameworks" without having yet a decent idea of what
> will be
> > Qt5 is impossible for me.
>
> actually, Qt5 is irrelevant to most of the work that needs to be done in
> frameworks. we can, and are, working against Qt4 right now. most of the
> work
> is modularization and modernization (while preserving source compatibility)
>
Ok, stupid question then. Why aren't we releasing this as kdelibs 4.8?
>
> we are merging some things upstream into Qt5, and the things that are
> merged
> upstream are going into a small temporary library call libinqt (lib in qt
> ;).
> when Qt5 arrives, that library will go away and we will be able to move to
> basing frameworks on Qt5. between now and then there is a lot of work on
> the
> modularization and modernization work.
>
> for instance, Sune's proposal to improve KNotification requires absolutely
> nothing from Qt5. having that done before Qt5 arrives would actually be a
> bonus as we wouldn't have to juggle too many different kinds of changes at
> once.
>
> i do recognize that there is not enough documented plans and direction for
> frameworks 5. there are a handful of wiki pages but they do not contain
> enough
> information; too much of that still resides in the heads of just a few
> people.
>
> to help address that, i'm hosting an irc meeting in a couple weeks with
> people
> currently working on frameworks 5 with the aim of pulling together clearly
> documented goals, tasks and milestones. the date has not been fixed yet,
> once
> it is i will announce it here as well so interested parties can join.
>
> i hope that with further documentation and clairty of goals that others
> will
> be able to see how they can get involved with frameworks and why now is a
> good
> time to do so.
>
>
I hope that, too :)
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Development Frameworks
>
[Attachment #3 (text/html)]
<br><br>
<div class="gmail_quote">2011/11/10 Aaron J. Seigo <span dir="ltr"><<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><br> <blockquote \
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" \
class="gmail_quote"> <div class="im">On Wednesday, November 9, 2011 23:44:21 Andrea \
Diamantini wrote:<br>> 4.x is where I'm living/fighting/coding/writing \
now.<br><br></div>for apps and workspaces, that is perfect. we don't want to \
disrupt app and<br> workspace development while we get kdelibs prepped for the next \
major release.<br> <div class="im"><br>> I'm sorry to say, in my mind next \
version of kdelibs is 4.8.<br><br></div>your mind is wrong. whatever the version \
number might end up saying (probably<br>to keep packagers and users from confusion) \
it'll be the 4.7 code base with<br> continued bug fixes applied :)<br>
<div class="im"><br>> And it will be based on the upcoming (not yet released) Qt \
4.8.<br><br></div>sure; but this is a non-relevant detail.<br> <div \
class="im"><br>> Thinking about "frameworks" without having yet a decent \
idea of what will be<br>> Qt5 is impossible for me.<br><br></div>actually, Qt5 is \
irrelevant to most of the work that needs to be done in<br> frameworks. we can, and \
are, working against Qt4 right now. most of the work<br>is modularization and \
modernization (while preserving source compatibility)<br></blockquote> <div> </div>
<div>Ok, stupid question then. Why aren't we releasing this as kdelibs 4.8?</div>
<div> </div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; \
PADDING-LEFT: 1ex" class="gmail_quote"><br>we are merging some things upstream into \
Qt5, and the things that are merged<br>upstream are going into a small temporary \
library call libinqt (lib in qt ;).<br> when Qt5 arrives, that library will go away \
and we will be able to move to<br>basing frameworks on Qt5. between now and then \
there is a lot of work on the<br>modularization and modernization work.<br><br>for \
instance, Sune's proposal to improve KNotification requires absolutely<br> \
nothing from Qt5. having that done before Qt5 arrives would actually be a<br>bonus as \
we wouldn't have to juggle too many different kinds of changes \
at<br>once.<br><br>i do recognize that there is not enough documented plans and \
direction for<br> frameworks 5. there are a handful of wiki pages but they do not \
contain enough<br>information; too much of that still resides in the heads of just a \
few people.<br><br>to help address that, i'm hosting an irc meeting in a couple \
weeks with people<br> currently working on frameworks 5 with the aim of pulling \
together clearly<br>documented goals, tasks and milestones. the date has not been \
fixed yet, once<br>it is i will announce it here as well so interested parties can \
join.<br> <br>i hope that with further documentation and clairty of goals that others \
will<br>be able to see how they can get involved with frameworks and why now is a \
good<br>time to do so.<br> <div class="HOEnZb">
<div class="h5"><br></div></div></blockquote>
<div> </div>
<div> </div>
<div>I hope that, too :)</div>
<div> </div>
<div> </div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; \
PADDING-LEFT: 1ex" class="gmail_quote"> <div class="HOEnZb">
<div class="h5">--<br>Aaron J. Seigo<br>humru othro a kohnu se<br>GPG Fingerprint: \
8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br><br>KDE core developer \
sponsored by Qt Development Frameworks<br></div></div></blockquote> </div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic