2010/11/29 Menon, Nishanth <[email protected]>: > On Thu, Nov 18, 2010 at 07:57, Marko Saukko <[email protected]> wrote: >> On 11/18/2010 03:46 PM, Peter Zhu wrote: >>> >>> Hi Peter Zhu, >>> The following change has been accepted. See the changelog below. >>> >>> Comments: >>> Thank you >>> >>> Thanks, >>> MeeGo Release Engineering Team >>> >>> [This message was auto-generated] >>> --- >>> Request #9576: >>> >>> submit: home:peter:branches:Trunk:Testing/u-boot(r3)(cleanup) -> >>> Trunk:Testing/u-boot >>> >>> >>> Message: >>> don't build against i586, BMC#10159 >>> >>> State: accepted 2010-11-18T05:46:16 peter >>> Comment: Thank you >>> >>> >>> History: new 2010-11-18T05:41:23 peter >>> _______________________________________________ >>> MeeGo-commits mailing list >>> [email protected] >>> http://lists.meego.com/listinfo/meego-commits >> >> Hi, >> >> Would it be possible to get some time to review the patches and things >> before they are accepted? In this case it took about 5mins (+- some mins >> what mail was handled by servers) to do this SR and accept thing as well as >> bugs.meego.com from NEW to RELEASED. I'm not asking to give 24hours for this >> kind of things, but could the community get for example 30mins to review >> what is going in before the patch is accepted? For example in this case this >> patch was not critical and nothing was blocked by it, in critical cases I >> can understand this but with this type of things would be nice to get some >> time to review. >> > > wondering on the status of this. what happens next?
I think QA is expected, ie, someone goes out and verifies it works properly for the FEA#'s in question. >From N900 side we've verified the tool support works in our acceptance images, so I guess the rest is verifying it works OK for actually booting. BR Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
