Skip navigation.
KDE Developer's Journals
Home

Should KDE PIM follow a separate release schedule / library requirements than the rest of KDE?

scott wheeler's picture
Submitted by scott wheeler on Sun, 05/09/2004 - 18:40
»

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mattr's picture

It's not this cut and dry.

Submitted by mattr on Mon, 05/17/2004 - 14:08.

I don't agree with the seperate release schedule, but I do agree with their maintaining KDE 3.2 compatibility (I know of no other library requirements), but since it seems this is more about the seperate release schedule than the library requirements, I picked "no" when my answer really would have been, "I don't like the seperate release schedule, but the compat with KDE 3.2 is nice"

My 2 cents.

»
cies's picture

I voted no

Submitted by cies on Wed, 06/30/2004 - 08:43.

I think the currently different of release scedule is an incident, isn't it?

To me a central release scedule seems a good thing, but maybe KDE will someday become to big for this 'ideal'.

»
superstoned's picture

I voted yes

Submitted by superstoned on Wed, 06/30/2004 - 09:52.

thats why I voted yes. It whouldn't be nice if the new version for kde pim whould be delayed because it has to wait for the whole kde to be finished. and the whole kde shoulnt have to wait for pim.

I think quite large parts of kde, like koffice and kde pim should be allowed to have a seperate release schedule - although they should try to keep it in sync with the whole of KDE.

»
20khz's picture

y

Submitted by 20khz on Sun, 07/04/2004 - 17:12.

yes.
we have already qt 3.3.2 (already tested) before kde 33.
so kdelibs+kdevelop should be released about a month or three before other pckages.

»

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.