Well, I am not expert on this, but I know that many of them are on holiday already.
This was done because we don't have either enough time or competent people to fix this before Meego 1.2 Timing relates also to the time that goes when you properly upstream stuff that has not yet been upstreamed. That has not been done yet because the said lack of people. Really complex issue and I know that the decision was not easy. I think it was accepted after all with the promise to fix it for 1.3 Br, //Harri ________________________________________ From: ext Wichmann, Mats D [[email protected]] Sent: Wednesday, December 22, 2010 10:07 PM To: Hakulinen Harri (Nokia-MS/Tampere) Cc: [email protected]; [email protected] Subject: RE: [meego-packaging] [meego-commits] 11064: Changes to Trunk:Testing/pulseaudio [email protected] wrote: > to Trunk:Testing/pulseaudio > > Hello, > > Before this topic goes way over it's significance: > > This happened because on certain product driven projects we are still > using mentioned PA 0.9.19 and Policy framework that is integrated > to that specific PA version. That is not something to be proud of, but > it is rather the reality of life in product scope. I think people could guess this (something coded to 0.9.19), but... why? >From pulseaudio.org, 0.9.19 was released 30 Sept 2009, 0.9.21 11 Nov 2009, and /every/ recent distro, including MeeGo, uses 0.9.21. Why would anyone then code to 0.9.19? The obligation of any project intending to be integrated into MeeGo is to stay current with the versions MeeGo is using. If someone suggested a product cricical project required downgrading the MeeGo kernel by a couple of steps, when it had otherwise been decided to be the target version, they'd be shouted down immediately. Why are we rewarding an incompetent development team who can't follow the rules in this case, then? _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
