RC Closed action points
From Symbian Developer Community
Back to main Release Council wiki page
| ID | Status | Action Description | Action Date | Assigned to | update | |
|---|---|---|---|---|---|---|
| RC230409_2 | CLOSED | Victor/Jim to clarify grant-back time for innovations for SFL and EPL. | Victor/Jim | see email
Victor responded by emailo and archived | ||
| RC230409_4 | CLOSED | Victor to distribute the release model details for ratification. | Victor | Click here to discuss
Link available in last RC minutes. Will be added to agenda for next RC meeting | ||
| RC230409_5 | CLOSED | Victor/Riku distribute existing Symbian and S60 Milestone definitions with SF milestones | Victor/Riku | This will be combined with RC230409_3 and this action closed. | ||
| RC230409_7 | CLOSED | Victor/Jim to validate that R&D license can be used to perform operator testing | Victor/Jim | see email | ||
| RC230409_8 | CLOSED | Victor to clarify if CDB, CBR are command line tools or eclipse plug-ins. | Victor | response can be found here | ||
| RC230409_9 | CLOSED | Riku to clarify if all Symbian 9.4 functionality is available standalone with no dependencies on S60. | Riku | response can be found in post meeting note
Riku: In general, components are available unless removed as a result of TPIP filtering. Source code still available for components which are not used by S60 but these won't be maintained by Nokia. | ||
| RC230409_6 | CLOSED | Victor to initiate the following offline actions
| Victor | Milestone defns - closed pending action RC230409_3: MSk will produce milestone defs material for review. Quality metrics - working group now set up. closed Requested | ||
| RC200509_1 | CLOSED | Update the status and issues of providing list of components (content of builds) at next RC meeting. This is an issue that should be shared with the community. | Jim | 23/06 some complexities in combining S60 and SymbianOS system models given restructure of codebase. List is now 80% correct – not yet complete or verified so shared with council members today but not ready for wiki. You can see which files belong to each package from S^1. | ||
| RC200509_2 | CLOSED | Riku to send list of TB9.1 post-branch content and defect fixes | Riku | 23/06 some TB9.1 changes were planned for post-branch from S^2 but actually included pre-branch, so no planned post-branch changes (of course this may change). Need discussion on process for injecting post branch changes as likely to happen in some release.
VP asked when will we start to see posting of defects through bugzilla? RM believes Nokia have started to publish showstoppers. Burden on package owner reduced as they are able to link to bug description in Mercurial. LLG asked what process was used to take in new content. VP explained that package owners need to guide it, we measure code churn + use bugzilla to track features. SF have started working through examples with package owners. | ||
| RC200509_4 | CLOSED | Jim to explain impact of OPENGL issue on emulator and HW and what we expect OEMs to do | Jim | 23/06 JC - issue solved as 2.0b release of S^2 included workaround for Graphics issues which is explained in the release notes, and documented in bug31; Have ported an OpenGL open source graphics implementation to allow emulator to work. NVidia should not be an issue for emulator post S^2. But NVidia is a key issue for delivery planning in S^3. | ||
| RC230409_1 | CLOSED | Victor to email requesting approval of council Change Requests. | Victor | click here to see vote thread.
Approval of Charter was via email. Victor to update forum wiki to indicate approval of Charter. Victor to check & update mailing list (some members missing). victor: Done - deleted the thread | ||
| RC230609_3 | CLOSED | Identify and publish technology area level test results relevant to S^2 from TB9.1 test results. | 05 Aug 09 | Riku | Riku sent update to the mailing lit | |
| RC230609_5 | CLOSED | Give f/b on critical and optional TPIP lists over the next week. | 03 Jul 09 | All RC members | email sent 26th June - Feedback Received by STE, DOCOMO and Fujitsu. Proposed to close the action based on this. | |
| RC230609_7 | CLOSED | Create milestones proposal ready for next RC call. | 05 Aug 09 | Mark | Proposal created, posted here, for discussion via forumhere. Approval to be requested at August f2f. | |
| RC230609_9 | CLOSED | RC members to vote on bug workflow proposal posted in release council web (2 weeks). | 10 Jul 09 | All RC members | Vote here. Voting time expire, no feedback received so we propose to implement the change and close the action | |
| RC230609_10 | CLOSED | Follow up putting HRP on plan, by next council mtg | 05 Aug 09 | Mark | TI has agreed to present Zoom2 plan at August f2f RC | |
| RC230609_12 | CLOSED | VP will start a discussion on the Forum about the criteria for functional completeness for S^3, including going to F&RC for key features. Please comment and will close by the end of next week. | 1 Jul 09 | Victor | discussion here | |
| RC230409_3 | CLOSED | Jim/Victor clarify the difference between VT4 and functionally complete. | Jim/Victor | 23/06: VP can make VT4 criteria received from Riku available to use as start point for group exercise to define Functionally Complete (FC).
MSk added that quality also needs to be considered. LLG Does the quality group produce def of FC? VP clarified that the RC should lead discussion through forums and need quality group to advise on what is measurable. VP encouraged all RC members to post comments and engage actively on discussion board. 20/08/09: FC criteria proposal circulated and Release Model updated. | ||
| RC230609_1 | CLOSED | Add agenda item for next teleconference: Process for including post-branch changes to release. (from discussion of RC200509_2) | 27 Aug 09 | Mark | This will be deferred to f2f RC end of August
20/08/09: The scenario now relates to post-FC changes and is not tied to post TB branch changes. The release model describes expected changes during the lifecycle, e.g. post-FC only bug fixes should be picked up. After the Stabilised milestone only critical fixes will be picked up.|| | |
| RC230609_4 | CLOSED | Get S^2 feature list from F&RC (IanH) and publish to RC | 05 Aug 09 | Victor | Ian is working on a 10 pager document for S^2. 1st draft to be available in August.
Release spec available. | |
| RC230609_6 | CLOSED | To capture the details of an integration plan for S^3 that includes the first PDk, Graphics and the Zoom2 baseport. | 05 Aug 09 | Mark | Draft plan created and sent for review by RC. Requires details of Zoom2 plan to be presented by TI at the f2f RC.
20/08/09: Updated release plan published. Zoom2 plan to be presented at RC mtg. Mitigation plan to be provided by TI is tracked by a new action RC270809_X|| | |
| RC230609_8 | CLOSED | Send out request for volunteers for Packaging Tools WG. | 05 Aug 09 | Jim | Raised at http://developer.symbian.org/wiki/index.php/Package_Management_Working_Group | |
| RC230609_11 | CLOSED | create the top items dashboard ‘RC landing page’ – for group contribution. Key technical tracks which are being worked on etc. | 10 Jul 09 | Urmi | see here. Propose the action is closed. All suggestions/contributions welcome. Need feedback and contributions by members | |
| RC050809_1 | CLOSED | Send an voting request to the Release Council Email list S^2 Functional Complete as PASS | 14 Aug 09 | VictorP | Sent email to the council asking for vote | |
| RC050809_3 | CLOSED | Present a proposal for SDK in S^2 at the next f2f. | 27 Aug 09 | UrmiS | Proposal published for review.
270809: Proposal presented and accepted (on proviso that S^2 SDK could be created at a later stage if needed. This was agreed). | |
| RC050809_5 | CLOSED | Start a discussion in the forums to provide feedback on the key features proposed for S^3 | 14 Aug 09 | VictorP | post your comments here | |
| RC050809_6 | CLOSED | Start a voting poll in the forums to ratify the proposed FC Criteria for S^3 | 14 Aug 09 | VictorP | vote here | |
| RC050809_7 | CLOSED | re-phrase the FC S^3 "must have" content criteria in the context of "Value of the release" | 14 Aug o9 | VictorP | done - see proposal here | |
| RC230609_2 | CLOSED | Report on process for taking in new content at next council. (from discussion of RC200509_2) | 05 Aug 09 | Victor | http://developer.symbian.org/wiki/index.php/Integration_Plan | |
| RC270809_2 | CLOSED | Jim/Mark to recommend that S^2 is official release and that RC will take the responsibility for approving subsequent Official Releases on behalf of the BoD. [Pending condition of the API definition and its linkage to Symbian - Official Release is linked to Trademark policy which requires existence of a compatibility test suite. Official Release status confirms that IPR is distributable.] | 24 Sep 09 | Jim & Mark | Discussions started in SF to action steps needed.
Action RC050809_2 is part of this. Update 110909: BoD had already declared S^2 an official release around the June timeframe. This was based on the candidate S^2 feature spec. For future releases declaration of "official" is not strongly dependent on FC being declared but does require the feature spec to be available so that the basis for the declaration is established. Clearly this means that this would occur around the FC for a release. The recommendation to move the responsibility of reviewing and declaring the official release status to the RC will be put to the BoD prior to S^3 FC. The availability of the compatibility test suite is being pursued via RC050809_2. Propose to close this action. | |
| RC270809_3 | CLOSED | All members to review and provide comments on the detailed Graphics integration plan by 11th September to Victor | 11 Sep 09 | All RC Members | Plan can be found in the release plan material embedded in the minutes of the 27 Aug f2f RC in Helsinki. Feedback received from Philippe Peruset (STE). No objections raised from any members. Laurent raised concern about testing on real HW. This will be raised as part of the Test WG | |
| RC270809_4 | CLOSED | Mark to talk to Ian Hutton about obtaining feature spec for S^3 (along same lines as for S^2) | 24 Sep 09 | Mark | The feature spec is generated around the time the release achieves FC and describes the total feature set, including the Key Features. One of the criteria for the FC is to ensure that the release has delivered the agreed Key Features which are initially defined at Release Start and may be modified after with agreement by the RC.
Update 110909: Confirmed with Ian. Discussion raised on Laurent (TI) proposal to review/approve detailed feature list at RS and then track deltas. This will be raised as a new action for Laurent to lead a forum discussion/workshop. | |
| RC270809_5 | CLOSED | Update Key Features list in line with the comments in the 27 Sep f2f minutes "Key Features required for S^3" section | 24 Sep 09 | Victor | This needs to include any breaks that should be tracked as well as listing what features of any phased rollout will be delivered, e.g. SHAI and SMP. The RC also needs to be told where to look for any other features it may want to include, such as TD roadmaps and Package Backlogs | |
| RC270809_6 | CLOSED | S^3 FC criteria discussion. Discussion around ‘agreed feature list’. Noted the following: - This should say "key feature list". KFs could change and should be under under change control by RC - We need to add the word ‘delivered’ to this statement - Remove ‘ratified by the FRC’ Update with the above clarifications. | 24 Sep 09 | Anders & Mark | 220909: Updated wording provided to RC members for comment | |
| RC270809_7 | CLOSED | Zoom2 plan. Riku noted that some of the TI code was below SHAI, some above. Pierre-Henri added that if TI wanted to protect features linked to hardware, perhaps the boundary should be at SHAI. Riku added that with the current licencing model, if there are good ideas which could be used for SHAI then they can’t be made available. Laurent to explore these suggestions and provide a response | 24 Sep 09 | Laurent | HRP sw contribution is not related to SHAI but to HRP provider IP diffentiators (HW+SW). In the same way nokia will not contribute all their above shai layer sw (their IP/differentiators), so hrp sw cannot be partitioned with shai.
This is a decision that TI needs to make in conjunction with the AC. | |
| RC270809_8 | CLOSED | Laurent to come back with an update to the Zoom2 plan within two weeks as stated in the TI chartpack | 11 Sep 09 | Laurent | Updated plan presented by Fred Blesser at RC conf call 240909. Plan progress will be tracked separately | |
| RC270809_9 | CLOSED | Matsuura-san asked which specific issue prevented SBS v1 (TPIP) from being included in the SDK. URMI to respond to this request | 24 Sep 09 | Urmi | Nokia are contributing SBSv2 (raptor) and this is what they plan to suport and make available under EPL.
SBSv1 is available under SFL, and so members are able to use it in S^2, and once the EULA has been agreed, it would be possible to make this available in the non-member PDK as well. However there are no plans to support it, or make it available under EPL. | |
| RC270809_10 | CLOSED | All council members to give feedback over the next 2 weeks on the content and schedule of the SDK/PDK plan | 11 Sep 09 | All RC Members | Confirmed that there were no objections | |
| RC270809_11 | CLOSED | Release model: Anders raised that some discretion may be needed in approving milestones, e.g. we could agree to passing FC knowing that a small feature still to be delivered – so it becomes an exception. | 24 Sep 09 | Mark | This shouldn't be part of the criteria as exceptions can always be the case. However, the notes could be used to describe this possibility.
Note added to release model to describe this | |
| RC050809_2 | CLOSED | Check with Daniel Rubio what is the level of compatibility of S^2 with Symbian^1 | 9 Oct 09 | Victor | Talked to Daniel. The AC has to define yet what is considered as public APIs. Once this is done, they will identify the public APIs in the SDK for S^1, and S^2 should run a compatibility assessment against it. The agreement is that S^2 and S^1 need to be compatible.
Public API definition being pursued by DM team and compatibility suite will be derived from existing S^1 suite. This will be enhanced to provide S^2 compatibility suite. Update 301009: Public API list made available on wiki. See http://developer.symbian.org/wiki/index.php/Symbian%5E2_Public_API_List AC has approved this list subject to clarification on supporting documentation. Also more information is being sought on the whitelist to identify why these breaks were approved. The compatibility test suite is being created by SF Delivery Management. | |
| RC050809_4 | CLOSED | Nokia to provide feedback on the likelihood of the key features being delivered in S^3 | 22 Oct 09 | Riku & Jussi | This will be on-going but S^3 KF list needs to be verified to ensure features are committed
Agreed to get closure 1 week before Oct f2f. Important to have good story on SHAI, SMP and NFC. Update 301009: Conflicting information over NFC availability in time for S^3. Jussi to confirm. This is being tracked by new action RC301009_6 | |
| RC270809_1 | CLOSED | Riku will update RC on the status of the plan for package owners to move to package based releasing and testing | 29 Oct 09 | Riku | Riku was hoping to have a plan for the 24thSep conf call. New view is to have plan for the Oct f2f.
Update 301009: Agreed to cover the testing part of this under the Test WG. As far as the package-based releaseing goes, processes and tools are expected to be in place by year end 2009. This describes how packages are released to Mercurial but not how we build PDKs (this will be covered by the foundation) | |
| RC270809_12 | CLOSED | All council members to read Jim’s Packaging Tools proposal and nominate suggested members of the WG | 24 Sep 09 | All RC Members | Request for participants posted here http://developer.symbian.org/forum/showthread.php?t=3011
More volunteers needed but close to a quorum. Need at least one PkO or rep. Riku will clarify the purpose of the WG with Jim. Update 301009: Team now identified. Jim to kick off. | |
| RC270809_13 | CLOSED | RC council members to propose volunteers for a Test WG proposal | 2 Oct 09 | All RC Members | Members proposed:
Test expertise on the team will also be provided by SF. Update 301009: Team identified except waiting for Nokia name to be confirmed. Overview of tesing provided by Jim in his blog. Kick off meeting to be held within next two weeks. Team to write mandate. | |
| RC240909_1 | CLOSED | Laurent (TI) to provide proposal for feature review and set up forum discussion | 9 Oct 09 | Laurent | This is to gather community opinions on the issue of ‘what is tracked’ in the feature list by the Release Council.
Update 301009: Laurent provided prooposal which was discussed at the RC tactical workshop on 29 Oct and will be progressed through actions from that. | |
| RC240909_3 | CLOSED | Provide high level plan for S^4 for review at Oct f2f | 22 Oct 09 | Urmi | Make available 1 week before the f2f
Update 301009: Done and reviewed at 30 Oct RC f2f. | |
| RC240909_4 | CLOSED | Start a forum to discuss showstopper defects | 2 Oct 09 | Matsuura-san | Main focus of this will be S^2 but definitions should apply generically to other releases. Forum started by Matsuura san.
Update 301009: Not many comments so far but initial list of showstoppers provided by Nokia. Forum will remain open for discussion. | |
| RC240909_5 | CLOSED | Members to put forward ideas for workshops to be held as part of the Oct f2f | 9 Oct 09 | All members | Some suggestions: Generating, reviewing & managing the detailed feature set for a release; WG sessions (this may require other attendees from member companies depending on who has been nominated to sit on WGs); etc....
Update 301009: Workshops held 29 Oct. | |
| RC240909_6 | CLOSED | Provide a list of 'showstopper' defects for S^2 in Bugzilla | 23 Oct 09 | Riku | This was originally agreed by Nokia but is still outstanding hence the creation of this action to track. A plan is needed for this.
Update 301009: Jussi confirmed that a list of showstoppers has been provided in Bugzilla. | |
| RC301009_1 | CLOSED | Add agenda item to RC meetings for MCP input. Also ensure that proposals pipeline page is updated to show which MCPs RC should review | 3 Dec 09 | Mark | Added to 101209 agenda (and will be on future agendas). Proposals pipeline updated to show MCPs for RC review. See http://developer.symbian.org/wiki/index.php/Proposals_pipeline. Email also sent to RC & Chairs with background on RC requirements of MCPs. | |
| RC301009_2 | CLOSED | Create a forum discussion by posting TI's proposal on the detail to be provided in each feature. | 13 Nov 09 | Laurent LG | Forum created here: http://developer.symbian.org/forum/showthread.php?p=11515#post11515 | |
| RC301009_4 | CLOSED | Clarify the plan for identifying 'real' breaks for S^2 | 13 Nov 09 | Sebastian B | Confirmed that break info will be available w47. Update 191109: Info here http://developer.symbian.org/wiki/index.php/Symbian%5E2_Compatibility_Breaks | |
| RC301009_6 | CLOSED | How many other TPIP items are remaining for S^2 (the ones listed for the FC were the 'must-haves'). Come back with a response to this. | 3 Dec 09 | Victor | Chris Davidson presented the status at the 10/12 RC meeting | |
| RC301009_7 | CLOSED | Confirm NFC availability and dates | 13 Nov 09 | Jussi A | Need to assess whether NFC will be available for S^3. Update 101109: NFC confirmed to be available for S^3 but delivery very close to FC. Plan being discussed to mitigate this but may need to investigate post-FC delivery.
091209 UPDATE: NFC not planned to make S^3 FC. Will be reviewed in 101209 RC call. | |
| RC301009_8 | CLOSED | Provide update to ZoomSW plan. Dependencies need to be understood | 20 Nov 09 | Laurent LG | Laurent sent update after the RC call | |
| RC301009_9 | CLOSED | S^4: Add delivery dates for KFs on the table (and ensure alignment with integration plan) | 3 Dec 09 | Urmi | Dates available for some features. Reviewed in 101209 call. Close as this is business as usual for creating S^4 plan | |
| RC301009_10 | CLOSED | S^4: prepare status update on RS for RC conf call in December with view for RC to ratify either at that call or before the Christmas break | 3 Dec 09 | Urmi | Status update available for review | |
| RC301009_11 | CLOSED | RC to feed back comments on Quality metrics and dashboard to QWG via qwg(at)lists.symbian.org email | 19 Nov 09 | RC members | One response received. Update 101209: First set of metrics has been released. Feedback can be made on these at any time via QWG. | |
| RCW1291009_6 | CLOSED | Set up call with RC to discuss next steps for actions RCW1201009_1 to _5 | 13 Nov 09 | Mark S | Call held 191109 | |
| RC101209_1 | CLOSED | Quality: How many of the defects raised against S^2 are raised by the community vs raised by SF | 9 Jan 10 | Victor | see email send on 14 Jan | |
| RC101209_2 | CLOSED | Quality: Take the critical S^2 defects to PkOs and get them to give their view on actual severity ASAP | 18 Dec 09 | Victor | this is being handle as part of the defect scrub | |
| RC101209_3 | CLOSED | CalDav info: send a link to the wiki page to the RC | 18 Dec 09 | Victor | see email send on 14 Jan | |
| RC101209_4 | CLOSED | Set up workshop for FC criteria including Quality and Testing and covering S^3 and S^4 | 9 Jan 10 | Mark | Workshop arranged for Jan 13th | |
| RC101209_5 | CLOSED | Summarise MCP information from RC and provide a way forward via email or forum | 23 Dec 09 | Mark | MCP summary sent to RC and council chairs. Will be reviewed at Jan RC f2f | |
| RC101209_6 | CLOSED | UI WG: Provide update on status via email to RC | 23 Dec 09 | Urmi | Update available at Tokyo RC mtg | |
| RC301009_5 | CLOSED | Lead a discussion via the RC Forum to clarify the conditions for 'Stabilised'. Set this going by 13/11. Review at next RC conf call 10th Dec | 13 Nov 09 | Chandra N | Mark emphasised that the intent is not to reopen the Release Model but to clarify these points. Chandra has posted the following discussion forum: Please see the following link, http://developer.symbian.org/forum/showthread.php?t=4124
We will review via the forum and also appears on the agenda for the Tokyo f2f, Jan 15th. Chandra presented Fujitsu's proposal on conditions for Stabilised. This was discussed with the RC (see minutes: http://developer.symbian.org/wiki/index.php/RC/2010-01-13_RC_meeting#S.5E2_Status_-_Victor) and a follow up action has been recorded: RC140110_4: Chandra N to update the definition and implications of the Stable milestone and publish for review by the RC | |
| RC240909_2 | CLOSED | Develop a strawman proposal for handling submission of features after FC | 9 Oct 09 -> 3 Dec 09 -> 14 Jan10 | Urmi | It is expected that any features delivered after FC will not be Key Features.
Update 301009: Strawman planned to be provided by next RC mtg (10th Dec) Update 101209: This should be discussed ahead of the S^3 FC but is not high priority at this point. Review at next call. Update 020210: thread to discuss impact and next steps created. Propose next steps at Feb call. http://developer.symbian.org/forum/showthread.php?p=15648#post15648 Update 240210: Have suggested an amendment to MCP Review Criteria (now posted here) to indicate which MCP would pose great risk for late integration. Also Propose an amendment to FC notes on Release Model to advise that acceptance criteria/plan for late integration of risky features should be provided at FC | |
| RC140110_2 | CLOSED | Nokia to identify PkO rep for defect scrub | 22 Jan 10 | Rauno U | Hari Lammi named | |
| RC140110_3 | CLOSED | TI to identify PkO rep for defect scrub | 22 Jan 10 | Laurent LG | Laurent will be the rep | |
| RC140110_5 | CLOSED | Define a subset of the S^3 FC test suite for S^2 Stable milestone Laurent & Fred Maurel have provided a proposal to the Test WG for use cases from TI as a starting point. | Mark S | The need for a S^3 FC test suite has been discussed with the Test WG. A subset needs to be selected for S^2. The need for S^3 test suite raised with TWG (TWG actions: 040210_4 AND 040210_6). When available a subset can be chosen for S^2. This will require input from the community. | ||
| RC140110_7 | CLOSED | Ask Chris Davidson to provide a TPIP update at the next RC meeting | 11 Feb 10 | Mark S | Chris will provided update offline. Will also provide update at f2f meetings. | |
| RC140110_8 | CLOSED | Fujitsu/Docomo to provide a contribution plan for submitting defect fixes to the SF | 15 Feb 10 | Matsuura-san | Plan submitted and will be reviewed at Feb call. | |
| RC140110_9 | CLOSED | Request FRC/AC to look at what core or critical apps are needed as a basic config for S^4 | 18 Feb 10 | Mark S | Urmi has discussed this with FRC. Salvatore Rinaldo and Urmi came up with as list of apps packages which would be regarded as key, in order to identify the must have items for UI migration. These are published in the current release plan and will be publshed on the wiki if required. | |
| RC140110_11 | CLOSED | Arrange call with SF to isolate cause of Zoom2 crash on boot-up of PDK3.0.e | 31 Jan 10 | Laurent LG | e-mail exchange made with SF. Compatibility break introduced by NGA under work also on emulator by SF in parallel. All latest info at: http://developer.symbian.org/wiki/index.php/Graphics_Package/KhronosReferenceImplementation. Crash investigation is ongoing work to be monitored in zoomII status in RC conf call / meeting. | |
| RC140110_13 | CLOSED | Provide a plan for S^4 pkg backlogs | 12 Feb 10 | Urmi | This is needed for S^4 planning info. Update 240210 - DUI package backlogs, breakdown of remaining key items provided in release plan slides. | |
| RC140110_14 | CLOSED | Define the content of the first S^4 contribution and the planned date | 12 Feb 10 | Urmi | Contribution planned for end March. Content will be defined nearer the time. | |
| RC301009_3 | CLOSED | Confirm AC ratification of S^2 Public APIs | 6 Nov 09 | Daniel Rubio | Definition of public APIs reviewed with AC. Final API baseline will be reviewed by email (plan by w49).
Additional APIs to be added and reviewed with the AC Thurs 25th Feb 2010. 4/3/10: No objections or comments raised by the AC to the final API list. Baseline is ratified by AC. See the following email | |
| RC140110_6 | CLOSED | Review the TPIP process/management to clarify the agreement on TPIP for S^2. Also propose any changes needed to ensure the process for TPIP agreements is clear | Victor P | Update 090310: the TPIP sheet has now a new column that clearly indicates what items will be delivered in what release vs what release is impacted by he IP whole |
Comments
Sign in to comment…
