Re: Release schedule proposal for the February MegaRelease

[Sune Vuorela]

On 2023-09-25, Albert Astals Cid  wrote:
> https://community.kde.org/Schedules/February_2024_MegaRelease
>
> Beta 1 is during Qt World Summit that is not ideal but I guess doable?
>
> I'll answer to this email with a few other emails things i thing we have to 
> discuss to try to organize the discusion earlier.

Will all of these points come with tarballs, or only from a certain
point?

/Sune

Re: KDE Gear repositories switching to Qt6 - Re: Release schedule proposal for the February MegaRelease

[Sune Vuorela]

On 2023-09-25, Albert Astals Cid  wrote:
> I'd vote for "need to be ready for RC1".

I'd say that this is at least the latest; but given how KDE is mostly
done by volunteers, I could imagine christmas holidays being a
productive time for many, so including that makes sense.

/Sune

Re: Fwd: KActivities repository split

[Sune Vuorela]

On 2016-02-18, Ivan Čukić  wrote:
> The transition period:
> -
>
> The situation with kde:kactivitymanagerd is clear, when making 5.20
> packages of kde:kactivities, please make the kde:kactivitymanagerd
> package to be a hard requirement

Wouldn't this create a circle of dependencies? kamd links kactivities,
and kactivities with a hard requirement of on kamd?

(We can't have circles)

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KDE Applications 15.12.0 available for packagers -

[Sune Vuorela]

On 2016-01-10, Albert Astals Cid  wrote:
> AFAIK prison is still not released so you either compile without it or get 
> the 
> code from git.

It's not. 

Maybe its maintainer should get their act together and do something
about it.

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: digiKam translations in l10n-kf5

[Sune Vuorela]

On 2015-09-22, Albert Astals Cid  wrote:
> releasing the same code forever makes no sense if people is supposed to be 
> using some other code.
>
> I'd like that you guys do some coordination with the rest of non digikam 
> people because otherwise packagers and developers get a mixed message of what 
> things are they supposed to use/package.

In the past, the solution has been to be a digikam release behind and
then unbundle all the libraries that digikam embeds. Unfortunately,
the digikam developers seems to be of the opinion that no one uses the
libraries like kexif, kipi and such, giving massive headaches to all of
us involved further down the chain of things.

Or maybe everyone should just stop using the digikam libraries, meaning
no exiv informations in gwenview. no kipi-integration in ksnapshot, ...
But maybe that's how the digikam developers wants it?

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: 4.14.1 packages up for packagers

[Sune Vuorela]

This was posted on irc:

if anyone runs in an issue building smokekde 4.14.1, this fixed it here 
http://paste.kde.org/phhu3tnwr 

It was asked to be put it on reviewboard. I don't know if it has happened.

/Sune

On Friday 12 September 2014 13:16:49 Eric Hameleers wrote:
 On Fri, 12 Sep 2014, Albert Astals Cid wrote:
  Hi, the 4.14.1 packages are up for packagers at the usual location.
  
  kde-workspace 4.11.12 is also included.
  
  Public release is next Tuesday.
  
  I have not yet built the packages since downloading them from limited
  akademy bandwidth is not an option.
  
  Cheers,
  
   Albert
 
 When building kdebindings, I run into these errors (akonadi 1.13.0
 installed in case that's relevant):
 
 [ 78%] Building CXX object akonadi/CMakeFiles/smokeakonadi.dir/x_7.o
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp: In
 member function 'void
 __smokeakonadi::x_Akonadi__ItemFetchScope::x_33(Smoke::Stack)':
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp:3454:32:
 error: variable 'Akonadi::TagFetchScope xret' has initializer but
 incomplete type
   Akonadi::TagFetchScope xret = ((const
 x_Akonadi__ItemFetchScope*)this)-Akonadi::ItemFetchScope::tagFetchScope();
  ^
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp:3454:120:
 error: invalid use of incomplete type 'class Akonadi::TagFetchScope'
   Akonadi::TagFetchScope xret = ((const
 x_Akonadi__ItemFetchScope*)this)-Akonadi::ItemFetchScope::tagFetchScope();
 
 ^
 
 In file included from /usr/include/akonadi/changerecorder.h:23:0,
   from
 /tmp/kde-build/kdebindings/smokekde-4.14.1/akonadi/akonadi_includes.h:16,
   from
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp:2:
 /usr/include/akonadi/monitor.h:37:7: error: forward declaration of
 'class Akonadi::TagFetchScope'
   class TagFetchScope;
 ^
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp:3455:62:
 error: invalid use of incomplete type 'class Akonadi::TagFetchScope'
   x[0].s_class = (void*)new Akonadi::TagFetchScope(xret);
^
 In file included from /usr/include/akonadi/changerecorder.h:23:0,
   from
 /tmp/kde-build/kdebindings/smokekde-4.14.1/akonadi/akonadi_includes.h:16,
   from
 /tmp/kde-build/kdebindings/smokekde-4.14.1/build/akonadi/x_7.cpp:2:
 /usr/include/akonadi/monitor.h:37:7: error: forward declaration of
 'class Akonadi::TagFetchScope'
   class TagFetchScope;
 ^
 make[2]: *** [akonadi/CMakeFiles/smokeakonadi.dir/x_7.o] Error 1
 make[1]: *** [akonadi/CMakeFiles/smokeakonadi.dir/all] Error 2
 make: *** [all] Error 2
 A
 
 What's happening here?
 
 Cheers, Eric

-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Fwd: KDE Frameworks Release Cycle

[Sune Vuorela]

On Wednesday 30 April 2014 21:39:36 Alexander Neundorf wrote:
  Especially with all the KF5 bits is versioned bound to each others (so
  that
  to fix a bug in one component, you need to update *everything* -
 
 are you assuming that or is this indeed the case ?
 Do all frameworks depend on the same version of all other frameworks, or do
 they have specific required versions ?

I haven't checked how it is done, I have only asked around how it is supposed 
to be done.

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Fwd: KDE Frameworks Release Cycle

[Sune Vuorela]

On Tuesday 29 April 2014 23:20:21 Lisandro Damián Nicanor Pérez Meyer wrote:
 The result will be that we will need to freeze at some point and do our best
 to keep up with patches for stable releases. Or maybe even drop KF5 for
 stable releases :-/

While I don't share the fatalistic point of Lisandro, I do agree that it 
brings potential problems. I do also expect a Debian to ship with a very 
patched-up set of KF5 packages. 

At freeze/stabilization point in at least Debian it is a time of 'bugfixes 
only, no new dependencies and features'. For a large collection of software on 
many architectures, a longer stabilization period is needed. 

Especially with all the KF5 bits is versioned bound to each others (so that to 
fix a bug in one component, you need to update *everything* - and all these 
bits of *everything* might have newer requirements of 'external libraries' and 
... oh the fun) it makes it often a simpler choice to just find the relevant 
patches and try to backport them, rather than pushing a entire new feature 
version (or maybe even 3 or 4 version numbers forward) and cross fingers that 
there are no regressions and none of the features introduces new grave bugs. 
(I know regressions and bugs never are planned, but my experience with 
software in general tells me that they happen. frequently.)

I do think we need a stable branch, and a stability period, and that it would 
make the primary customers (the distributions and their users) able to ship a 
better product closer to what we as KDE upstream thinks our product should be.

I do think that we are failing if we are putting the task of backporting 
patches on the shoulders of people who doesn't know the involved code in 
details.

Or, to put it another way, I don't think we can (or should) force users of KF5 
to choose to do their products in a rolling release model. 

So quite many users will end up using patched-up versions of KF5. That should 
not be our goal.

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Late feature plan addition for Ark?

[Sune Vuorela]

On 2013-10-31, Raphael Kubo da Costa rak...@freebsd.org wrote:
 I would like to do that as soon as possible, and since many of them are
 feature additions or UI changes there should have been an item in the
 4.12 release plan for Ark saying Merge Basyskom's changes to Ark
 listing Lamarque and me as the responsible people.

 Would the release team be OK with that so that we don't have to wait for
 yet another release cycle?

I think that it would be nice to have some sort of proposed timeline,
e.g. do you plan to merge them by the end of the weekend or by
christmas?

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Removing features before KDE 4.11 release

[Sune Vuorela]

On 2013-06-23, Filipe Saraiva filip.sara...@gmail.com wrote:
 Scilab backend for Cantor is broken because Scilab support to standard
 streams is broken too. My question is, can I disable this backend now,
 before KDE 4.11 stable release?

How is it broken? Is it broken with all versions of scilab or only with
some specific versions? Can it be fixed easily? by 4.11.1 ?

If it is broken beyond repair, I think it should be disabled. If it can
be fixed, I think we should try to go that route. If it is only broken
for some software combinations, we should try to disable it for
non-working combinations.

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Exception for Nepomuk Ebook Indexers

[Sune Vuorela]

On 2013-06-20, Albert Astals Cid aa...@kde.org wrote:
 So let's please discuss how we're going to fix the copied code for 4.12 and 
 if 
 we find something that makes sense we can go forward with the exception.

I thought the plan was to make the plugin api public for nepomuk-core
for 4.11 so that plugins don't have to live with nepomuk-core, but
rather could live with what they work with

I guess that has changed. Are there any plans of making the plugin api
(and abi) public for 4.12 in nepomuk-core ?

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Review Request 108516: Do not hardcode site-packages for the python libdir.

[Sune Vuorela]

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108516/#review25911
---


$ python -c from distutils.sysconfig import get_python_lib; 
print(get_python_lib(True, prefix='/usr/'))
/usr/lib/python2.7/dist-packages

is on a debian system. I think that might be right.

- Sune Vuorela


On Jan. 21, 2013, 11 a.m., Michael Jansen wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 http://git.reviewboard.kde.org/r/108516/
 ---
 
 (Updated Jan. 21, 2013, 11 a.m.)
 
 
 Review request for Build System, Release Team and Kevin Kofler.
 
 
 Description
 ---
 
 Do not hardcode site-packages for the python libdir.
 
 
 Diffs
 -
 
   cmake/modules/FindPythonLibrary.cmake 
 7cef79b16521c759f38f1deea539a28a50c5d708 
 
 Diff: http://git.reviewboard.kde.org/r/108516/diff/
 
 
 Testing
 ---
 
 Not much. Works the same as before. Need someone to check on debian. Need 
 someone to check when installing into /usr.
 
 I think the strequal to check if PYTHON_SITE_PACKAGES_INSTALL_DIR is 
 different from PYTHON_SITE_PACKAGES_DIR is not optimal but good enough. The 
 only problem could be a trailing slash or different case on windows. Any 
 hints to improve it?
 
 
 Thanks,
 
 Michael Jansen
 


___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Akonadi-Nepomuk Feeder Improvements

[Sune Vuorela]

On 2012-12-26, Christian Mollekopf chrig...@fastmail.fm wrote:
 As the feeders so far are IMO just broken, I think we can consider this a 
 bugfix and should get it into 4.10.

if they are just broken, maybe fixing them with git rm for 4.10 is a
better approach ?

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Release Team BoF Summary

[Sune Vuorela]

On 2012-07-15, Jorge Manuel B. S. Vicetto jmbsvice...@gentoo.org wrote:
 So, can you please use - and not ~. The - character has a
 special meaning on versions for us. The ~ character can cause issues
 for us, as we use it when specifying dependencies on other packages as
 a fuzzy version dependency.

So. Bottom line here is that if '-' (dash) is used to separate version
from 'prerelease string', the debian and ubuntu and modern rpm land will
have to fudge the versions. if '~' (tilde) is used, then gentoo will
have to fudge the versions. Old rpm land will probably have to fudge the
version in both cases.

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Release Script (KF5)

[Sune Vuorela]

On 2012-07-12, Martin Gräßlin mgraess...@kde.org wrote:
 My understanding is that there won't be a kde-runtime once there is=20
 frameworks.

Correct. Runtime bits go to the libs that has them as a implementation
detail.

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: bic and sic change in soprano

[Sune Vuorela]

On 2012-05-29, Aaron J. Seigo ase...@kde.org wrote:
 as Trueg is perhaps MIA for a few more days and i'd like to see this move 
 forward sooner rather than later, has anyone figured out what commits removed 
 this class(es?) ...

mainly 3d66d429cb48781881af3e735f2a80af2114ab25, but
5dde64227186d405f86bf66256705fbceabcf1e2 also has some related bits.

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

bic and sic change in soprano

[Sune Vuorela]

Hi sebastian

Someone just noticed that we have a bic and sic change in soprano (removal of 
tcpclient).

As discussed quite a bit earlier, soprano is part of the kdelibs abi  api 
(due to how nepomuk in kdelibs is implemented), so it is effectively a abi  
api breakage of kdelibs.

We have promised abi and api stability of kdelibs, so this change is in 
violation of our promises to the world.

Thanks in advance for investigating

/Sune Vuorela
-- 
How can I do for resetting the 6X DirectX mousepad?

The point is that you neither can ever forward from a pointer, nor have to 
debug the USB file for saving a file of the operating system over the pointer.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: adding kwebkitpart to KDE SC

[Sune Vuorela]

On 2012-03-25, David Faure fa...@kde.org wrote:
 Todo:
 1) In the projects.kde.org database, we would need to make kwebkitpart a
 child of kde-baseapps.

 Who can do that? Do I need to file a sysadmin request, maybe?

Yep. I would expect it to have to go over kdereview ...

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Request for splitting oxygen-icons tarball

[Sune Vuorela]

On Sunday 26 February 2012 21:24:16 Max Brazhnikov wrote:
 Hi,
 
 Can you please stop packing scalable icons or pack them in a separate
 tarball? They are not needed for building anyway and downloading them is
 just a waste of time, bandwidth and disk space for those who build KDE
 from sources.
They're needed for license compliance, and it is really nice that they are in 
the same source tarball like the rest. Please keep it this way.

/Sune
-- 
Man, do you know how to rename the line from Excel 95 and from the tools 
inside MS-DOS?

The point is that you neither must ping a SIMM over the AT gadget, nor ever 
have to load the fan for disabling a DirectX system.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Request for splitting oxygen-icons tarball

[Sune Vuorela]

On Sunday 26 February 2012 23:29:37 Max Brazhnikov wrote:
 Does debian's oxygen-icon-theme package, which contains only png icons,
 violate the license? 

No. just like debian's systemsettings package, which contains compiled code 
also doesn't violate the license.

In both cases, the sources is a apt-get source away. In both cases you get the 
tarball created by Dirk

 What's the difference then?

that's hopefully obvious.

/Sune
-- 
Do you know how can I reset the RO SMTP shell from Netscape 4.5.3?

The point is that from the control tools menu inside Photoshop you must ping a 
connection of a connector to a SMTP pin over the parallel mouse, so that then 
from the control panel menu within ICQ you should click a pin in order to log 
from the mousepad.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KNotes to Extragear?

[Sune Vuorela]

 Well, It's not like it's going away, if it's just moved to extragear, users 
 wont even notice, because it's handled at the distro level.

hah. Don't expect distros to magically pick up extragear applicaitons
(and suddenly maintain them) just because you don't...

/Sune

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Add some apps to the 4.7 release?

[Sune Vuorela]

On Saturday 14 May 2011 21:28:40 Thomas Zander wrote:
 good evening people,
 
 I've been stabilizing and making ready for release some apps (in git) and I
 would like to get them released in the 4.7 release compilation.
 Can you help me get through the steps to make this possible? Thanks.

Hi Thomas

I'm a bit unsure how to interpret your request. Do you want the apps to be 
released along side the released compilation or as part of the compilation?

I basically see 3 kind of apps:
Apps in the software compilation (okular, kopete, dolphin, ...)
Extragear Apps released along side of the compilation (rsi-break, ...)
Extragear Apps with own release schedule (kdevelop, amarok, previous koffice 
releases)

I'm unsure wether you want to move into group 1) or group 2).

/Sune
 - who has a handful of reasons for disliking 1), but no reason to bring it up 
if that's not what the request is about.
 - and btw, not a release team member
-- 
I'm not able to rename the editor of a program, how does it work?

You neither should mount the Ultra 3Dfx e-mail, nor need to receive the floppy 
disk for exploring with a SCSI clock.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KDE 4.3 RC1 preparations

[Sune Vuorela]

On Tuesday 23 June 2009 11:58:23 Tom Albers wrote:
  d) kdepim tarball splitting is now finalized?

 Afaik kdepim/akonadi is completely standalone now, so that tarball can be
 created yes.

 But iirc akonadiconsole depends on one or two classes in kdepim/akonadi and
 we have no idea if that is a problem or how to solve that.

Yes. It would be a problem, if it still was the case. Luckily Christophe 
Giboudeaux says that it is fixed already, so nothing to worry about.

/Sune
-- 
Man, do you know how may I remove the directory from Explorer 5.5?

First from the control drawer menu inside Excel you either should never 
reinstall a FPU of the SIMM over the pin, or never need to telnet to the 
coaxial computer to disable the CPU.



signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

[Sune Vuorela]

On Thursday 04 June 2009 03:07:48 Benoit Jacob wrote:
 kdeedu (step) relies on the development version of eigen, that will
 become eigen 2.1.
 but eigen 2.1 won't be released before kde 4.3.

I'm quite puzzled by this, especially since it, as I see it, was Eigen people 
who ported step from gmm to eigen.

I see the following possibilities:
1) step don't get released with 4.3.
2) eigen people start to work fast to revert the porting of step to eigen back  
 
to gmm
3) eigen people start to work fast to get a stable release out before 4.3,   
maybe just backporting the needed things to 2.0 ?

I really think that packaging a snapshot or packaging unstable releases is the 
very wrong approach here.

/Sune
-- 
Do you know how to doubleclick with the hard disk to the display from 
Photoshop 5000?

You should never receive a TCP/IP board for overclocking the GUI.



signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

[Sune Vuorela]

On Wednesday 03 June 2009 23:23:13 Maciej Mrozowski wrote:
 On Wednesday 03 of June 2009 22:24:05 Ingmar Vanhassel wrote:
  At least kdebase-runtime [1], and kdebindings [2] fail here if I use the
  latest soprano release. Is soprano trunk required or will a soprano
  release follow?

 Further yet unstatisfied (but at least listed in CMakeLists.txt)
 dependencies for 4.3 seem to be:
 - yet unreleased eigen for kdeedu/step
 - yet unreleased sip/PyQt4 for pykde4
 - trunk phonon for mplayerthumbs to work with phonon backend (and not
 mplyer executable - this one is optional though)

 If some of them are not going to be released before 4.3, well... packagers
 (for source based distros at least  - eigen is purely build time dependency
 so may not bother binary distros) may need to either hold 4.3 releases or
 release snapshots of dependencies on their own.

Phonon was discussed earlier, and it was said that phonon is not going to get 
a release until the Qt 4.6 release.

/Sune
-- 
How can I log from the microkernel to a line?

From Redhat MkLinux or from the folder inside MS-DOS you either have to 
receive a mail, or can never forward to the RAM POP3mail mousepad in order to 
insert the file of the driver.



signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: KDE 4.2.5?

[Sune Vuorela]

On Friday 29 May 2009 18:26:26 Allen Winter wrote:
 Howdy,

 Can we decide now if there will be a 4.2.5 release?
 If not, then that saves us some unneeded backporting work.

 Recall we stopped at 4.1.4.
 IMO we should stop at 4.2.4.

 Let's decide very soon and I'll communicate the decision to all developers.

I would like to request something in between; still do some backports, but 
only in some special cases, at least until 4.3final is out.

The special cases I could imagine would probably be something like:
 - grave bugs (dataloss  too frequent crashes to make the app usable and 
such) - and maybe with a CCMAIL: kde-packager 
 - gcc 4.4 (and such)  compile fixes.
 - maybe other cases that I haven't yet thought of, but of a similar 
severity and impact.

That way, distributions and others who cares can get blessed backport 
patches of the problems, which is kind of preferred.

/Sune
-- 
How to close the sendmail?

You must send the digital gadget, this way then from Mandrake MkLinux you 
neither should ever cancel a laser BIOS operating system on a pointer to the 
folder to a SCSI wordprocessor, nor can ever ping the window over a processor 
to reset the SIMM.

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

What to do and not do in third digit releases

[Sune Vuorela]

Hi

Some of you do probably not know me, while others do. I'm one of your friendly 
debian packagers. (Occasionally, I'm also one of your unfriendly debian 
packagers, but that's hopefully rare)

When looking at 4.1.2 which is tagged and about to be released, there is a new 
kind of change that we haven't earlier seen in the point releases. I don't 
remember seing any discussions about it, so I'm bringing it up here.

The third digit releases is as far as I know bugfix only releases.

But here in 4.1.2, there is major changes to kdegraphics, to be more precise 
the libkdcraw library which has been rewritten and breaking ABI and having a 
soname bump.

These changes are apparantly required for the upcoming digikam release (which 
might or might not be released before kde 4.2 gets released)

As this library isn't in kdelibs, but in kdegraphics, there isn't as such a 
policy against breaking binary compability in this module, but doing it in a 
third digit release might be something different.

So, I guess the release team should decide in between the following:

1) Branch is feature frozen, the changes should be reverted, but are welcome 
for kde 4.2 series.

2) Digikam is a so special app that it need a exception to usual policies for 
making it easier to do digikam (pre-)releases. 

3) Change the policies of third digit releases in general and allow many more 
new features in.

I personally would advocate 1. Let the new features and SONAME bump (and 
digikam) wait for kde4.2.

Getting a decision within the next days is quite important, as it is related 
to the kde4.1.2 release.

Thanks for your time

/Sune
-- 
How to ping to the POP clock?

You never have to connect the 2D front-end to a code and from Windows you 
either must doubleclick the BIOS, or must telnet to the tool on a GUI of the 
3D kernel on a analogic hardware in order to forward from a GUI.


signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: breaking BIC for new addon libs in minor releases (was: Re: Goals? How are we doing?)

[Sune Vuorela]

On Friday 09 May 2008, David Faure wrote:
 On Tuesday 06 May 2008, Tom Albers wrote:
  Op dinsdag 06 mei 2008 18:46 schreef u:
   Am Dienstag, 6. Mai 2008, um 18:39 Uhr, schrieb Tom Albers:
Op dinsdag 06 mei 2008 18:30 schreef u:
  I disagree. I think it is a must to be BC between minor releases.

 Not for a rarely-used lib like one that kdeutils would provide, IMHO.

Wearing my distro packagers hat, not being binary compatible is acceptable 
*IF* you remember to also bump the SONAME

/Sune
-- 
How might I explore the software from AutoCAD 2.9 and from the control panel 
inside Office?

You should never mount the URL and you either have to reset a server of a PCI 
system, or can never ping the GUI on a computer over a driver to the DirectGL 
pointer, in such way from Explorer 8000 you neither must turn on the laser 
login, nor need to insert the graphic attachment for telnetting from a AGP 
mousepad.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Delaying KDE 4.1 Alpha 1 ?

[Sune Vuorela]

On Sunday 20 April 2008, Tom Albers wrote:
 Hi Guys,

 On the agenda for this week is the tagging of Alpha 1. As I understand from
 IRC the fallout from the plasma hacking event is pretty big and the current
 state is less than what we want to display to our alpha testing user base.

 I know KDE is /a lot/ more than plasma, but I feel the overall perception
 of KDE in reviews and perception of users is largely based on Plasma. I
 think we should delay Alpha 1 until this is fixed. Any ETA on that would be
 great.

Why not roll back to working plasma instead?

/Sune
-- 
How can I forward to a SIMM?

You either must link the forward, or have not to log on a wordprocessor of the 
Ultra SCSI password on the monitor to debug the space bar.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

Re: Move kwalletmanager?

[Sune Vuorela]

On Thursday 10 January 2008, Urs Wolfer wrote:
 On Thursday 10 January 2008 19:29:39 Stephan Binner wrote:
  On Thursday 10 January 2008 15:37:33 Allen Winter wrote:
   The kwallet seems like a critical app that should always be available
   in our base system.
 
  More critical than kmix? :-) Wanting to say, kmix belongs there too imo.

 Yes, I agree. Both kwalletmanager and kmix belong to kdebase.
 I think kdebase/runtime would be the correct place for these.

Please not. runtime is already too big.

runtime is the stuff needed by all kde apps.

I don't need kmix for anything. if I use okular, some game or ... in a 
non-kde4 environment, I will not have any need kmix.

I can easily be convinced that it would fit in kdebase/apps, but not in 
kdebase/runtime.

I would like though to get the font configuration tihngie (kcmshell4 fonts) 
in -runtime.

/Sune
 - who runs kde3, but uses okular currently
-- 
Genius, I cannot turn off a kernel from Outlook 2.8, how does it work?

From DOS and from the control tools menu within Word XP you should never 
install on the submenu but therefore you neither can ever forward to the 
editor over a memory, nor should mount a fan for renaming the GPU to the 
graphic firewall of the Fast monitor.


signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team