On 17 Jan 2011, at 13:53, Zhu, Peter J wrote: >> -----Original Message----- >> From: Anas Nashif [mailto:[email protected]] >> Sent: Monday, January 17, 2011 9:35 PM >> To: Zhu, Peter J >> Cc: [email protected]; Li, Peng; [email protected]; >> [email protected] >> Subject: Re: [meego-packaging] [meego-commits] 12054: Changes to >> Trunk:Testing/libxcb >> >> >> On 17 Jan 2011, at 10:30, Zhu, Peter J wrote: >> >>> It's asking for a new version of so basic package just before one week off >> feature freeze. If you look how many packages has build dependency on this, >> it's a huge list. >>> >> >> What other deadline would have the submitter had to comply with? Isn't that >> the who idea of having a feature freeze deadline? >> > I don't say it's too late. I don't reject this. It's just a fact. It's a > basic package, right? Just like kernel/Xserver/Mesa/Toolchain, they should be > stable as early as possible in a release cycle. >
To comfort you, we are getting a new rpm package with lots of changes, much more critical than libxcb :) Anas > Peter > >> >>> So my question is: >>> 1. Does new meegotouch-compositor really have use >> xcb_discard_reply()? Could we use another way to do same thing? >>> 2,. If we have to does anybody ever know how many API/ABI changes for >> 1.5->1.7? Does all packages using libxcb build successfully against new 1.7? >> Does it really work for 1.7? >>> > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
