Re: KDE Dev Platform Status
On Sunday 25 November 2007, Sebastian Kuegler wrote: We should tap into coolo's experience here. My proposal would be to have one last BIC (but SC) monday. That should get us the critical stuff/fallout, and not break things. I hope. Aha. Why did we release the platform if we break BIC one last time? Either we keep BC or we don`t. Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
On Monday 26. November 2007 17:53:17 Dirk Mueller wrote: On Sunday 25 November 2007, Sebastian Kuegler wrote: We should tap into coolo's experience here. My proposal would be to have one last BIC (but SC) monday. That should get us the critical stuff/fallout, and not break things. I hope. Aha. Why did we release the platform if we break BIC one last time? Either we keep BC or we don`t. Why can be answered as 2 different things; 1) Because there are some showstoppers that can be fixed in a MUCH better way when BC is ignored. 2) Because there is nobody 'out there' that will find it a really big problem if we do break BC before we make a final release for the simple reason that this exact released version will not be in any distro's official release. So, the real question is why not allow this for critical bugfixes. (and those only, obviously or else we'll need one in 2 weeks again). ps. one such bug I'm thinking about is the kactioncollection one (151421) -- Thomas Zander 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 Dev Platform Status
Am Sonntag 25 November 2007 schrieb Albert Astals Cid: A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. That much about the theory. In practise no-one will develop KDE4 applications at this point and is not willing to touch them anymore, so BIC should not matter at all. As long as KDE4 isn't installed on people's machines, ISVs (3rd party developers) won't ship binaries linked against it to people, so people won't care if updating KDE4 breaks apps that do not exist. SIC are a big problem though. But for BC, you have to keep in mind what you're doing it for, not just follow the rules because they've always been followed. Greetings, Stephan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
A Diumenge 25 Novembre 2007, Allen Winter va escriure: On Saturday 24 November 2007 18:23:21 Albert Astals Cid wrote: A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. Albert, Of course I agree, in theory. But we also need to acknowledge that we are not all-knowing super-geniuses with unlimited time and man+woman power. I don't think we need to be so hard on ourselves. I'm not beign hard, just realistic-pessimistic. I try to use KDE 4 everyday and i can't and i can't fix all things because i'm not a super-genius with unlimited time. So my suggestion is just to ignore we released kdelibs 4.0, make the BIC changes and release kdelibs 4.0.0 again. And besides i would want to suggest that KDE 4.0 should not be released on 11 december, but i won't do it and expect some crazy fixing goes along trunk and fixes everything for that date. Albert IMO we have a very short time window to implement critical BIC changes. And critical BIC changes that require no source code changes are even easier to approve. Anyway, that's my opinion. -Allen PS. moving libexec/kdesu to bin/kdesu would break the Dev Platform freeze. Do I continue with the co-installability stuff? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
On Sunday 25 November 2007 10:03:03 Stephan Kulow wrote: Am Sonntag 25 November 2007 schrieb Albert Astals Cid: A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. That much about the theory. In practise no-one will develop KDE4 applications at this point and is not willing to touch them anymore, so BIC should not matter at all. As long as KDE4 isn't installed on people's machines, ISVs (3rd party developers) won't ship binaries linked against it to people, so people won't care if updating KDE4 breaks apps that do not exist. SIC are a big problem though. But for BC, you have to keep in mind what you're doing it for, not just follow the rules because they've always been followed. We should tap into coolo's experience here. My proposal would be to have one last BIC (but SC) monday. That should get us the critical stuff/fallout, and not break things. I hope. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 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
KDE Dev Platform Status
Howdy, Are we willing to permit BIC changes to the Dev Platform? If so, under what conditions? There are still requests coming into k-c-d for BIC changes to kdelibs and I'm sure there have been such changes since the hard freeze went into effect. For example, ossi's KCoreConfigSkeleton patch.. I'm inclined to allow this patch. ossi says it is safe and SC. and aseigo says he has a use case for it. I need some guidelines for allowing patches to the Dev Platform modules. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE Dev Platform Status
A Diumenge 25 Novembre 2007, Allen Winter va escriure: Howdy, Are we willing to permit BIC changes to the Dev Platform? The question you need to make yourself is: Did we release the 4.0.0 for the Dev Platform?, techbase says yes, so the answer to that question is no BIC changes until 5.0.0 Obviously you can ignore that we said to have released 4.0.0 for the Dev Platform and call it that was our 4.0.0 joke platform and then allow BIC changes. Albert If so, under what conditions? There are still requests coming into k-c-d for BIC changes to kdelibs and I'm sure there have been such changes since the hard freeze went into effect. For example, ossi's KCoreConfigSkeleton patch.. I'm inclined to allow this patch. ossi says it is safe and SC. and aseigo says he has a use case for it. I need some guidelines for allowing patches to the Dev Platform modules. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
