Milestones and schedule
Milestones are builds that have passed integration testing and will be made available for download and trial. A milestone can be promoted to a beta after an additional week or two of production use.The milestone and release candidate (RC) schedule is as follows:
- 2011/08/22 - Milestone 2
- 2011/09/12 - Milestone 3
- 2011/10/10 - Milestone 4
- 2011/10/31 - Milestone 5
- 2011/11/21 - Milestone 6
- 2012/01/09 - Milestone 7
- 2012/01/30 - Milestone 8
- 2012/02/20 - Release Candidate 0
- 2012/03/05 - Release Candidate 1 / Beta 1
- 2012/04/02 - Release Candidate 2
- 2012/04/23 - Release Candidate 3
- 2012/05/07 - Release Candidate 4
- 2012/05/14 - Release Candidate 5
- 2012/05/21 - Release Candidate 6
Overview
Rational Team Concert forms the developer focused role of our Rational solution for Collaborative LifeCycle Management. Rational Team Concert success has grown at a rapid pace and this growth has created the need for managing very large deployments. For the next release, we intend to focus on three areas including improved enterprise deployment, scaling and reliability, enhancements for customers developing complex and embedded systems, and improved consumability and usability.Themes
The following themes guide the planning of this release:Application LifeCycle Management - Enterprise Deployment and Reliability: A key advantage of the Jazz platform approach to application lifecycle management is that it can help lower cost of ownership by centralizing the administration of ALM across an enterprise. Our customers are embracing this simpler Jazz platform approach and are deploying much larger communities of users. As more users are deployed, the need for high availability of those services also grows. In this release of Rational Team Concert, we intend to support automated high availability that leverages WebSphere clustering capabilities (169830) Although the primary goal of this work is to automate high availability, the underlying use of clustering will also allow us to begin to exploit horizontal scaling of Rational Team Concert and CLM applications across more distributed servers.
Application LifeCycle Management - Enterprise Scalability: High availability addresses the enterprise need for availability of users but what about the growth in complexity of the projects being managed? In this release we intend to also introduce planning across projects (169425). Plans are currently limited to iterations inside a project area in RTC 3.0.1 but in this release, we intend to allow users with master plans to track tasks in other project areas. The primary use case for this work is to be able to plan development execution of a cross cutting feature that spans more than one RTC project area. Managing more data means managing more queries. To make it easier to manage many query variations in a single query, we intend to allow queries to support input variables (169822). Do you also have external web based data sets that you would like to use as input to work item custom fields? If that is the case, we plan to allow input from external HTTP value set providers (169820) giving you more flexibility in managing enterprise data sets.
Systems Market Support - Variant Management: Many of our customers develop complex or embedded applications that require managing many release variants at the same time. One example of this is when you need to deliver a bug fix to a series of release streams and you need a way to verify you have done this to all the variants of your software. We plan to make it easier to find all the streams where a given change set has been delivered. (169818)
Systems Market Support - Security and Permissions: Often a complex hardware/software development effort involves collaboration across teams spanning outside suppliers who may be delivering parts of a broader solution but all working on the same project area. This requires the ability to provide more flexibility in configuring read access for any combination of users, team areas, and project areas. In this release, we intend to support "access groups", which are a collection of project areas, team areas, and users (170132, 169933) that can be shared at the repository, project area or team area level. A related issue is the need to control visibility to versioned artifacts at the folder or file level and not just at the SCM component level. In this release we intend to make that possible (169819). Some customers also need to be able to delete artifacts for security or other reasons. In RTC 3.0.1 we introduced the ability to delete work items and in this release we intend to add support for deleting versioned SCM artifacts (169816).
Systems Market Support - Workspace Management: More flexible SCM load rules for customers who need to load components into on disk workspaces that are laid out differently than how they are stored in the repository is also planned. We intend to allow users to save complex load rules to a file and store them for re-use across teams. You can read more about this feature in our New & Noteworthy.
Consumability and Usability - Simple Versioning: Many extended team members can benefit from taking advantage of versioning, so it would be beneficial to these users to keep the interfaces to versioning simple and easy to use. We intend to add a Windows 7 Explorer integration to provide SCM services targeted at non-developers with simple locking and versioning support using a familiar file system view. (169838).
Consumability and Usability - Kanban Method Taskboard: Our customers employing lean and agile methods have also asked us to provide Kanban Method support in RTC. Kanban Method helps to optimize the ideal flow of work through the system using a "pull" model and answers questions like "Where is capacity available" and "Am I exceeding my desired limits?" We intend to deliver this by providing a Kanban Method taskboard planning view which will allow limits to be set on state flows in the taskboard viewer. (170002)
Consumability and Usability - Any platform. Any IDE. One ALM Toolset: We intend to continue to extend our rich developer experience from the Rational Team Concert Client for Microsoft Visual Studio IDE (169839) as well as Eclipse based IDE's such as Rational Developer for System z/Power Systems (169843). We also plan to make performance and usability enhancements for mainframe users of the ISPF client (169841).
Consumability and Usability - Enhanced Build, Promotion and Deployment: We intend to make available the dependency build, promotion and deployment capabilities previously only available on z/OS on other platforms, starting with IBM i (169845). In addition we plan to enhance build, promotion and deployment by allowing build output (binaries) to be stored in the SCM (169817).
Consumability and Usability - Hudson Build Engine Support: Rational Team Concert supports incremental adoption which is a key aspect of consumability for different project needs. In keeping with this theme, we intend to extend support for Hudson as a build engine for RTC which should make migration of your build easier if you choose to adopt Rational Team Concert. (169829). With these planned changes we intend to allow development teams to have a built-in choice of build engines that best meets their needs from continuous integration through enterprise solutions such as the Jazz build engine, Hudson, Microsoft Build Engine (MS-Build) and Rational Build Forge. You can use any of the build engines and have RTC manage build health and reporting.
For more details about the corresponding plan items for these themes, view the detailed release iteration plan.
Notices
References in this material to IBM products, programs, or services do not imply that they
will be available in all countries in which IBM operates. This material, including any plans
contained in the material, may change at any time at IBM's sole discretion, based on market
opportunities or other factors, and are not intended to be a commitment to future content,
including product or feature availability, in any way. Statements regarding IBM's future
direction or intent are subject to change or withdrawal without notice and represent goals
and objectives only. Please refer to Terms of Use for more information.
© Copyright IBM Corporation 2008-2011. All rights reserved.
댓글 없음:
댓글 쓰기