Presentation is loading. Please wait.

Presentation is loading. Please wait.

Agile Evolution - We Heard Your Feedback Current Plan

Similar presentations


Presentation on theme: "Agile Evolution - We Heard Your Feedback Current Plan"— Presentation transcript:

1 Agile Evolution - We Heard Your Feedback Current Plan
Aug – Aug. 2020* 16.10 with 3 years support Teradata Database 16.10: Offers 3 years of maintenance from GA plus 2 years Extended Maintenance Replaced the original plan of standard 4 months of support with no EDM 2018 – 2021* 16.20 with 3 years support New Features Teradata Database 16.20: Also offers 3 years of maintenance from GA plus 2 years Extended Maintenance Includes feature updates, replacing previously planned minor releases (16.50, 16.60, and 16.70) Streamlined path for maintenance fixes and features integration with bi-weekly maintenance updates When we released Teradata Database 16.10, we have decided to shift our support plan so it would be supported for 3 years, replacing the original plan of 4 months of support without EDM. For Teradata Database 16.20, we are also offering the years of support,. We are also adding feature updates to the release, and we are streamlining and simplifying the maintenance plan that should facilitate more predictable and simpler upgrade and maintenance planning for our customers. * and are supported for 3 years from their GA dates. © 2018 Teradata © 2018 Teradata

2 Teradata Database 16.20 Support Plan
Teradata Database will be supported for 3 years from the GA date + Extended Database Maintenance (EDM) No change to the current EDM support plan Maintenance Updates will be provided on-demand Will have release number of xx.yy GA Support: 3 years EOM 2018 2019 2020 2021 2022 2023 EDM: 2 years Let’s dive into the details of the plan, one by one. Similar to 16.10, Teradata Database will also have a 3-year support period from its GA date, followed by a 2-year Extended Database Maintenance. In terms of the EDM, there’s no change to the current support plan. It will be provided as on-demand basis, and will have release number using the 4th set of digits. © 2018 Teradata © 2018 Teradata

3 Teradata Database 16.20: Feature Updates
Feature updates include new features / enhancements and fixes After the initial release of 16.20, 2 more feature updates were planned approx. every 4 months They replaced previously planned 16.50, 16.60, and releases No dictionary changes Incremental changes through smaller updates reduce risk and testing efforts Feature update 1 Feature update 2 3 years GA In addition to the maintenance releases, Teradata Database will have 2 updates that include new features and feature enhancements in addition to fixes. These feature updates do not include dictionary changes. These 2 feature updates are planned to be released approximately every 4 months following the GA of 16.20, and they will replace the previously planned 16.50, 16.60, and releases. ***********INTERNAL NOTES **************** Current plan is to have 2 feature updates. If the 3rd feature update is going to be released, it will be communicated. Approx. 4 months Approx. 4 months Feature updates EOM © 2018 Teradata © 2018 Teradata

4 Teradata Database 16.20: Release Numbering
Each update (including the two with new features) will be identified with the 3rd set of the release number (e.g ) Each update is a cumulative update of previous update releases 16.20.xx 16.20.xx 16.20.xx 16.20.xx 16.20.xx 16.20.xx 16.20.xx 3 years GA So now that you have an understanding of maintenance updates and feature updates, let me go over quickly about how they are numbered. After the initial release of 16.20, each of the updates – both the maintenance and feature updates – are numbered using the 3rd set of release number, like , 16.20,02, and so on. As I mentioned in the maintenance updates slide, each of the updates is a cumulative of all previous updates. Maintenance updates Feature updates EOM © 2018 Teradata © 2018 Teradata

5 Updated Release Plan for Teradata Database 16.20 Summary
Teradata is enhancing our existing release and support plan with Teradata Database 16.20: Teradata Database will be supported for 3 years from its GA plus Extended Database Maintenance (EDM) Two (2) Feature Updates with new features are planned Approx. every 4 months after the GA Will have xx version numbering They replace previously planned 16.50, 16.60, and releases No dictionary changes during the entire xx series Incremental changes through smaller updates Maintenance Updates will be delivered every 2 weeks and replace current Maintenance Requests (MRs)and generic E-Fixes In summary: Teradata Database will be supported for 3 years from its GA date, plus 2 years of Extended Database Maintenance. After its release, Teradata Database will have 2 more updates that will contain new features and enhancements without dictionary changes. These feature updates will essentially replace the previously planned releases of Teradata Database 16.50, 16.60, and These feature updates will be numbered xx. These feature updates are incremental in the nature compared to the traditional major/minor releases we’ve done in the past. During the 3-year maintenance and support period, there will be bi- weekly maintenance updates. © 2018 Teradata © 2018 Teradata

6 Teradata Tools and Utilities (TTU) Releases
TTU will continue to have monthly rollup releases Monthly rollups will contain both features and fixes Monthly rollups will not deprecate features 2 forward and 4 backward compatibility with Teradata Database No change TTU 16.20: Teradata Database 14.10, 15.00, 15.10, 16.10, 16.20, 17.00*, 18.00* TTU uses a simplified version numbering model TTU xx will support all Teradata Database XX releases Simpler for customers and partner products: Forward and backward compatible with whole Teradata Database release series Install the latest TTU xx version for use with Teradata Database XX features Partner certification with the latest TTU release will suffice for the series Teradata Tools and Utilities (or TTUs) will basically continue to have monthly rollup release. These rollups will continue to have both features and fixes and will not deprecate features. It will continue to offer 2 forward and 4 backward compatibility with Teradata Database. So TTU will be compatible from through 16.20, plus the next 2 database releases. All TTU xx releases will support all Teradata Database 16.20xx releases. * Anticipated Teradata Database major release numbers; subject to change © 2018 Teradata © 2018 Teradata

7 Release Version Numbering Comparison between 16.20 and Pre-16.20
16.20 structure: XX.YY 16 is major release 20 is minor release XX is maintenance or new feature update YY is patch (either site specific e- fix or EDM only) Pre structure: XX.YY.ZZ.n XX is major release YY is minor release ZZ is MR maintenance release n is patch (generic and site specific e-fix) ************* INTERNAL NOTE ********************** Pre-16.20 ZZ: MR contains customer-requested and internal medium/high risk fixes N: generic e-fixes contains low risk customer-requested fixes until each MR is released and after last MR until EOM. Site specific e-fixes provided/approved on request 16.20 XX: Maintenance updates contain customer-requested and internal low risk fixes. Feature updates contain customer-requested and internal medium/high risk fixes. © 2018 Teradata © 2018 Teradata


Download ppt "Agile Evolution - We Heard Your Feedback Current Plan"

Similar presentations


Ads by Google