KDEPIM in SC 4.5, or "who can we piss off the least?"

[Eli Wapniarski]

If KDEPIM 4.4.x can still run wiht KDE 4.5 then we can get everything other 
than the newest KDEPIM. I believe that this has been the method used in the 
past.

Eli

On Saturday 15 May 2010 08:47:46 Ryan Rix wrote:
> Hey all
> 
> Please see http://thomasmcguire.wordpress.com/2010/05/14/akonadi-meeting-
> and-the-kde-sc-4-5-release/
> tl;dr: KDEPIM in 4.5.0 won't be ready due to the KMail2 Akonadi port, and
> will be shipping in 4.5.1
> 
> What does this mean for us? Well, as happened in 4.4.0 days, we're going
> to start getting a bunch of our users gearing up for 4.5, and being ultra-
> hyper-super-excited to try all the new shinies, especially the kdepim
> goodness everyone has been hyping up.
> 
> I am kind of thinking that we should put some *real* thought into this
> issue, as I'm sure that either way we handle this, there will be much
> wailing and gnashing of teeth; on the one hand we have our no-we-want-
> centos-style-updates group which will be upset by us pushing 4.5 to
> anything but rawhide, and those that will be upset if we -don't-, so I
> think we should get out in front of this issue now, rather than Beta or RC
> rolls around.
> 
> I know that I don't really show up for SIG meetings, due to school, so I
> am kind of out of touch on what exactly our plans are for 4.5 or if we
> even have any yet. But summer is around the corner (today is my last non-
> finals Friday in high school!) so I will begin attending SIG meetings
> regularly. I'm willing to own this kdepim issue if only partially, as I am
> close to upstream KDEPIM for my GSoC project. I will be assessing KDE
> trunk this weekend, and can provide at least a partial report of
> regressions in the non-KMail PIM stack.
> 
> One option that I see is tearing KMail out of the PIM packages in kde-
> redhat/unstable, so we have kdepim 4.5 and kdepim-kmail 4.4. Keeping that
> in kde-redhat allows us to hack on it without having to put kdepim-kmail
> through review. Of course, that all depends on how well KMail1 interacts
> with its akonadi brethren, an issue which tmcguire kind of left in the
> open.
> 
> I'm wondering a little if 4.5 is a good time to address our updates policy
> in general, a time to promote kde-redhat (maybe there is some way we could
> promote it more prominently on the SIG page and elsewhere?) and keep our
> 4.5 updates there until 4.5.1 or even 4.5.2 for stability's sake and to
> keep certain factions on the devel list from whinging when they lose
> $petfeature, or decide that 150MB of KDE 4.5 is enough to start Yet
> Another Thread about, or they decided that Akonadi sucked and disabled it
> and oops-where's-my-calendar... That last part is of course written in
> jest, but similar things did happen for 4.4, and I think that handling
> this far ahead of time is a good way to try to regain some face among the
> rest of Fedora, whether we deserved to lose face in 4.4 or not.
> 
> Best
> Ryan

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.