Hi,

Please read this after my earlier message on this topic.

>________________________________________
>From: Wichmann, Mats D [[email protected]]
>Sent: Wednesday, December 22, 2010 7:42 PM
>[email protected] wrote:
>> On Mon, 20 Dec 2010 04:33:40 -0800 (PST)
>> Vivian Zhang <[email protected]> wrote:
>> ..
>> Message:
>>     Reversion to 0.9.19 and apply the patches from UMG (BMC 11252)
>>
>> ..
>>
>> Ok, I will sacrifice myself for the benefit of saying what no one else
>> appears to be willing to say, but...
>>
>> WTH!!!!
>>
>> Downgrading a version of one of the core architecture elements seems
>> completely broken to me!  Why are we doing this, especially since we
>> already have officially released 1.1 with 0.9.21 version of PA?
>>
>> I assume there are MeeGo 1.1 -> 1.2 upgrade plans/paths, so how will
>> this go when we are downgrading the API version?
>>
>> What about those who have already started developing plugin modules to
>> the 0.9.21 API, I assume all these will be at risk for breaking
>> too?!?!
>>
>> I mean really, how can we even be willing to consider this, or
>> am I just being completely dense here (or missing some key, as yet still 
>> secret
>> or embarrassing piece of relevant details)?
>>
>> Seriously?
>
>No comments on this?  Seems like a really bad idea to me, too.
>0.9.21 was actually remarkably stable for a project which still
>isn't completely mature - just now 0.9.22 is out which means
>.21 lived for a year.  .19 was apparently buggy and was replaced
>quickly.

The PA "0.9.19" version in question (with the Policy system) is 
"borrowed" from some product program as I said before.

It means that it includes some patches to original .19, and some of
those are related to stability as well as to some other things.

Certainly, that is not "clean" or "pure" way to go, but as far as I have
understood this issue, the mentioned combination is really product
level implementation. Of course, that still needs to be proven with
MeeGo 1.2 stack on our normal QA process.

Anyway, I am more like messanger here, so please don't shoot me..

Br,
//Harri





 




_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to