On Tue, Nov 8, 2011 at 11:18 AM, Aaron J. Seigo <[email protected]> wrote: > On Monday, November 7, 2011 19:32:15 Dawit A wrote: >> >> Well this is over a month too late, but I have a enhancement change >> >> for kcookiejar that needs to go into kdelibs/kioslave for KDE 4.8. The >> >> patch has actually been pending for a merge since KDE 4.6. See >> >> https://bugs.kde.org/show_bug.cgi?id=54300. > ... >> Right. The patch simply moves the idea of session cookies from being a >> global configuration option to a site specific option. That is it gets >> rid of the all or nothing approach currently employed. That gives the >> user a lot more control of how they deal with cookies. > > can you explain why it must go into 4.8? it's been waiting since 4.6, and i > didn't find a description of what requires it in 4.8 ... > > as far as i can see, it's a feature enhancement that isn't strictly required > by anything (though it is very nice to have indeed), so it should go into the > frameworks branch.
That is fine for the kdelibs portion, but what do you suggest be done with the kde-baseapps portion of the patch ? Wait until 4.8 gets branched ? With all the pending framework changes coming, I would be surprised if the patch would not end up falling through the cracks. I hate to see some one's good work, which I am is useful to many users, go to waste like that. Anyways, I personally do not have any specific reason for this patch going into the 4.8 release except to state that I won't have the time to see it merged past that release point. Someone else would have to pick it up and do it, which I very much doubt will happen. There are very few developers that are interested in working on the low level stuff in KDE.
