Hi all, Just a reminder for the LRM meeting tomorrow. I would like to prioritize all remaining tickets in the next 2 calls - tomorrow & next week - to finalize what we are taking up in 2.3 and what stays for the next version. I agree that we need to discuss & understand the details before finalizing what needs to go in which release, but may be good if we keep the discussions to a minimum to be able to make the decision on prioritizing without going into the details of the proposals, so that we can cover all the tickets in the 2 calls. Most of the errors in the LRM can quickly be fixed without needing much discussion. If you are wondering how to interpret the tickets, I am putting the ones that go into LRM 2.3 as "Urgent", the ones that we may include depending on available proposal and approval in committee - but not considered extremely critical as "high" and the rest either i leave it as "new" or "acknowledged" in the system. So under the "P" column in the database, the urgent ones come with a red double hat mark and high as single hat. I have updated the details from the last conference call in the mantis database. Regards, Sri -- Srikanth Chandrasekaran Design Technology (Adelaide) Freescale Semiconductor Ph: +61-(0)8-8168 3592 Fax: x3201Received on Tue Oct 25 01:40:44 2005
This archive was generated by hypermail 2.1.8 : Tue Oct 25 2005 - 01:41:37 PDT