Hi,
was RC1 already prepared/tagged? KDEPIM has a major regression in maildir
handling in it. We are working on that (and actually Sergio reverted the
commit (3f86351c2082cbcabc897dfceac95496b7876cf0), so I'd be glad if the hotfix
is in RC1.
Not having it causes VERY slow Kmail behavior and
On Sunday, October 02, 2011 17:04:42 Dirk Mueller wrote:
Hi,
I just finished uploading KDE 4.7.2 tarballs. Unlike previous
tarballs, these have been consistently taken from KDE/4.7 branch in
git.
What does this mean, no 4.7.2 tag was created in git?
I don't see anything like that with git
On Sunday, December 19, 2010 13:31:26 Allen Winter wrote:
Also: We strongly recommend that distros use Akonadi 1.4.90 along with
RC1 and KDEPIM 4.6 beta3.
This is actual a requirement, not a recommendation. kdepimlibs 4.6 will
not compile with earlier akonadi releases.
Andras
On Wednesday 21 January 2009, Dirk Mueller wrote:
did we agree on doing the Qt 4.5 update after KDE 4.2.0 is out (as in
released, not only tagged?).
I think it makes sense. We can make 4.2.1 work correctly with Qt 4.5 if
there is need for patches on the KDE side. And yes, released, not
On Tuesday 20 May 2008, Dirk Mueller wrote:
So from kdewebdev kimagemapeditor, kfilereplace, and kxsldbg should
be released?
Kommander can be also released.
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
signature.asc
Description:
On Tuesday 06 May 2008, Andreas Pakulat wrote:
Well, we could probably do that, but without any guarantees regarding
binary compatibility. Especially not for the interfaces, shell,
project, sublime, language and vcs libraries.
Yes, this is a problem. But still would be nice to release, like e.g
On Monday 05 May 2008, Matt Rogers wrote:
- KDevelop and KDevplatform modules
=We should remove this goal, I guess?
I don't know. We tried hard to get to a point of being releaseable,
but we're not there yet. (or people are too picky). I'll see about
pushing the point this week.
On Monday 05 May 2008, Allen Winter wrote:
I guess kdereview should be closed for now?
Sorry, but kdereview is also for apps that want to move to extragear.
So it doesn't make sense to completely close it.
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment -
On Saturday 03 May 2008 10:55:18 Andreas Pakulat wrote:
As before the 4.0 release this also affects kdewebdev/quanta, which also
can't be released due to the dependency on kdevplatform (and they're not
ready either). I don't know the state of other apps in kdewebdev, so
just disabling
On Sunday 20 April 2008, Aaron J. Seigo wrote:
but a contingency for a plasma (or even workspace as a whole if
that's easier? crappy for the kwin guys though =/ ) from the 10th is
probably smart.
That's not that easy. I tried to compile now trunk without updating
kdebase, and kdepim fails to
On Friday 18 April 2008, Friedrich W. H. Kossebau wrote:
I guess we agree that every program should have some kind of active
maintainer, some people who feel responsible for it and have
sufficient knowledge about it, if it is included in a KDE module.
This would be the ideal world. But even
On Monday 31 March 2008, Sebastian Kügler wrote:
FWIW, we're having a plasma sprint during the same weekend (10th -
15th), I take it we might get away with the occasional feature
addition as well?
And the KDevelop Hackaton is also around that time (12-18th of April).
So yes, please move the
On Sunday 30 March 2008, Alexander Dymo wrote:
Because everyone here is using the word scripting language
that automatically implies somewhat condescending point of view on
Python, Ruby and any similar languages.
Sorry, in the beginning I couldn't find the good word, but in fact I
meant
On Saturday 29 March 2008, Nicolas Ternisien wrote:
Yes, and where did you find your binary Qt 4.4 version to compile KDE
4 ? You compile it too from SVN.
Don't get silly. Qt 4.4 IS available in binary form if you want to use
it:
Hi,
The short answer is that I'd like to not see such apps in the main
modules. With main I mean something that you must build and install to
have a usable KDE.
On Thursday 27 March 2008, Allen Winter wrote:
Do we allow Python/Ruby/C#/Perl etc. apps in the KDE main modules?
If so, which
On Friday 28 March 2008, Nicolas Ternisien wrote:
Why will your Python app will use something new in the KDE API before
having the binding ready and updated ? Moreover, changes in the KDE
API will only massively be done for major version (KDE 4 -5), and in
this case, all KDE source code will
On Friday 28 March 2008, Andreas Pakulat wrote:
As soon as you allow one scripting language in a main KDE module
you'll basically have to allow all or try to fight all those naggers
that file thousands of reports asking for their preferred language.
BTW, will it be strange when I will ask to
On Friday 28 March 2008, Allen Winter wrote:
1) must perform: speed-wise and memory-wise
I'd like to add here that those apps should not be resident apps (apps
that need to run continuously). I'm not saying that such applications
cannot be written in scripting languages, but they should not be
On Friday 28 March 2008, Allen Winter wrote:
That would eliminate Jonathan's print config tool from consideration.
Do you really mean kdebase-runtime?
I know, and this is what I meant. Of course IMO.
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment -
On Friday 28 March 2008, Rex Dieter wrote:
rationale being?
(because this seems to target system-config-printer-applet that
jriddell's been working on, which I'd really really like to see).
The rationale is that the interpreter executable needs to be permanently
in the memory. And if we allow
On Friday 28 March 2008, Andras Mantia wrote:
PS: I will test this and guidance once my KDE trunk checkout finished
compiling.
And I failed. printer-applet has some dependencies (python-cups, hal-
cups-utils) that I couldn't find for my distribution (opensuse). This is
already a problem. So I
On Friday 28 March 2008, Jonathan Riddell wrote:
bindings (or wrong interaction between PyKDE and python-dbus)
Trolltech says the issue causing this should be fixed in Qt 4.4 RC1.
That's good news.
- it uses a different translation method
It uses gettext, same as kdelibs. See above for
On Tuesday 25 March 2008, Dirk Mueller wrote:
On Friday 21 March 2008, Andras Mantia wrote:
as of now, kdesupport is not branched (except for 3.5), nor it is
tagged. This can cause confusion as see on this thread:
http://lists.kde.org/?l=kde-develm=120587525306937w=2
one shouldn't use
On Tuesday 25 March 2008, Tom Albers wrote:
I think it is the responsibility of the kdesupport library maintainer
to clearly indicate which released version of their library should be
used to compile branch and trunk. So I'm against branching, tagging
or releasing.
But then, why do we have
On Tuesday 25 March 2008, Mark Constable wrote:
I can imagine this is why kdesupport came into
being in the first place, something that can be reliably fetched
automatically with standard tools.
Exactly, this is my idea. If you want to build trunk, you use kdesupport
from trunk and you can
On Tuesday 25 March 2008, Tom Albers wrote:
I just don't see the need, if the kdesupport authors request it, it's
a totally different discussion though.
Where are kdesupport apps developed? In /trunk/kdesupport? In other svn
servers? Again why do we keep it here, if it is how you said? Or why
Hi,
as of now, kdesupport is not branched (except for 3.5), nor it is
tagged. This can cause confusion as see on this thread:
http://lists.kde.org/?l=kde-develm=120587525306937w=2
I'd like to propose either tagging a version of kdesupport with each
KDE release (tagging a version that is
On Friday 15 February 2008, Stephan Kulow wrote:
Hi,
.. is on ktown for the packagers to grab since tuesday.
So it looks like we can start rollout :)
Thank you for doing it, and sorry for the problems we caused!
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop
On Friday 01 February 2008, Stephan Kulow wrote:
Hi Allen,
just discussed it with Albert - to avoid FOSDEM weekend, I would tag
on 13th to release on 19th. Fine with everyone?
I think this is a good plan.
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment
On Saturday 12 January 2008, Helio Chissini de Castro wrote:
We need talk again with Joris, but remember, keg maintainers are free
to do releases in between. We can push the same releases again in the
launch, no issue.
Having mid-term releases is allowed for everyone. The question is if
they
On Thursday 10 January 2008, Allen Winter wrote:
ark seems core to me
At least in KDE3 we had ioslaves for reading compressed files. I think
that's enough for a basic desktop.
we already decided that a calculator is part of our core desktop.
I don't see why not kcalc.
Yes, we decided that
On Thursday 10 January 2008, Allen Winter wrote:
I almost think that ark, kcalc, kgpg, kfloppy, and sweeper
could go into kdebase as well.
I don't think so. Of course they are nice additions to the desktop, but
I see no reason why they should be in kdebase. After all one can use a
different
On Wednesday 05 December 2007, Dirk Mueller wrote:
On Wednesday 05 December 2007, Sebastian Kuegler wrote:
A matter of Dirk including it, not sure what went wrong the last
time, but it probably wasn't intentional.
I was waiting for kdevplatform dependency to be removed, which did
not
Hi,
there was a discussion in October about this issue, but as someone
brought my attention to it (I build from svn and didn't read the whole
announcement), it seems that kdewebdev was still missing in RC1.
I'd like to see a kdewebdev tarball in 4.0 (RC2 and the rest) with the
following
On Wednesday 28 November 2007, Rex Dieter wrote:
So, do *you* want to be the one to tell the event organizers that all
their hard work and effort to pull the event together is now in
jeopardy? Not I.
No, I don't, but this is shows clearly how bad is to do a time based
release for a *new*
On Monday 26 November 2007, Dirk Mueller wrote:
As i said, it enters and endless loop on start, so i did not test
anything.
KNumber::operator quint64(void) const seems to call itself if you
are on a 64 bit machine like i am.
So, how about debugging and fixing that issue?
Attached
On Wednesday 10 October 2007, Andras Mantia wrote:
On Wednesday 10 October 2007, Andras Mantia wrote:
KDE 4.0 should NOT contain:
- Quanta (and that would remove the dependency from kdevplatform)
- Kommander (it is already disabled from compilation)
kxsldbg was also not ported yet
Hi,
Until now I was sure that kdewebdev will miss completely the 4.0
release. Recently from a discussion on kde-devel, I learned that Paulo
managed to get KLinkStatus from there perfectly usable for 4.0 and he
would like to see it released together with KDE 4.0.
How should we proceed in this
On Tuesday 09 October 2007, Albert Astals Cid wrote:
I already explained, remove the confusion caused when smart sites
link to the changelog and say kde has been removed.
But as you say, they are read/write for anyone, feel free to remove
the exit.
I did so.
What if somebody links
On Tuesday 09 October 2007, Dirk Mueller wrote:
On Tuesday 09 October 2007, Andras Mantia wrote:
Only Quanta depends on kdevplatform at this moment.
parts that can be disabled? if we can remove the kdevplatform
dependency then I'd just release a kdewebdev tarball.
otherwise I'd add
On Monday 01 October 2007, Tom Albers wrote:
I don't want want to flame as you request, but could you consider
moving kdevelop to extragear-sdk? In that case you can determine for
each release if you want to be part of it. We will just tag what is
in there at that moment so you can swap around
On Monday 01 October 2007, Stephan Kulow wrote:
Am Montag 01 Oktober 2007 schrieb Andras Mantia:
On Monday 01 October 2007, Tom Albers wrote:
I don't want want to flame as you request, but could you consider
moving kdevelop to extragear-sdk? In that case you can determine
for each
On Sunday 06 May 2007, Tom Albers wrote:
Op zo 6 mei 2007 12:13 schreef u:
So... does the silence means agreement? :)
I still fail to understand what you want. You want to the
release-team to do releases for you and you want to do your own. You
want a common library but dont want to follow
Hi Giovanni,
I forwarded your message to the release team.
Release team, please read the (beginning of the) message.
Andras
On Friday 20 April 2007, Giovanni Venturi wrote:
Is it possible to delay the kde 3.5.7 tagging later than 30th April?
There are too much messages in KDevelop (about
On Tuesday 06 March 2007, Stephan Kulow wrote:
messages/kdewebdev/kommander.pot
messages/kdewebdev/quanta.pot
In KDE4 there is no kommander yet (its disabled from compilation). But I
don't understand if this list is the obsolete list, or just listing
everything? Because Quanta exists and it
On Monday 05 March 2007, Alexander Dymo wrote:
The feature freeze date is totally unrealistic for KDevelop. I can't
speak for other applications, but I guess they'll have troubles too.
That's actually fine. We can delay KDevelop release till KDE 4.1.
As normal, same here for KDEWebDev.
But
On Tuesday 06 March 2007, Stephan Kulow wrote:
People hear my message: STOP IT! NOW!
May I continue? ;-) Yes, I agree with the idea of setting up milestones,
and I don't care that much if we cannot make KDevelop and Quanta4 ready
for KDE 4.0, after all there is time and life after that it is
47 matches
Mail list logo
