Agile Evolution - We Heard Your Feedback Current Plan

Slides:



Advertisements
Similar presentations
How does Microsoft approach change management communication? What happens when I have an outage? What is the Service Health Dashboard? What is the future.
Advertisements

Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
SE 555 Software Requirements & Specification Requirements Management.
Media Partners.
What are your questions and feedback? What happens when there is change or a service incident? What is the Service Health Dashboard? What is our communications.
IGrafx – General Terms of Use. Trial Software Licenses For test purposes only Not for normal business use Training based on the trial software is also.
9/10/20151 Hyperion Enterprise 6.5 New Features & Functionality Robert Cybulski, CPA Finit Solutions.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
HP-PPM Project & Portfolio Planning
1 SCO Update Service Kerri Wallach, SCO Services Product Manager April 16, 2003.
Oracle Patching and Maintenance A practical guide for System Administrators October 2009.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
SWE.org. Not what we wanted to hear … but we needed to listen Some choice findings from our initial member survey “Make the material more user friendly.
GEONS Ground Support System Java 7, JavaFX and the NetBeans Platform supporting NASA Missions Operations.
EGEE is a project funded by the European Union under contract IST WBS/ Execution Plan Alistair Mills Grid Deployment Group
Software Testing Process
Teradata Upgrade – Version May 16, Executive Summary Business Problem: SPHE has Teradata as the primary database for the HORIZON data warehouse.
3 rd Party Ad Serving POV What’s the F’ing Difference?
ONE LAPTOP PER CHILD This works are licensed under a Creative Commons Attribution 2.5 License. One Laptop per Child Builds, Customizations and Localization.
Founded by Big Five Consulting ex-employees Oracle Gold Partner Focus on PeopleSoft 15 years of PeopleSoft experience Worked in both technical and functional.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Zscaler Support Best Practices Guide Version September 27, 2016.
보안 취약점 비교 Linux vs. Windows
Business Intelligence Energy, Resources and Utilities.
Veritas End-of-Life (EOL) Policy Quick Reference Guide
Software Development.
Introduction to CAST Technical Support
FIXED ETHERNET SWITCH COMPARISON TOOL (v6- presentation mode will activate tool) The information in this document is confidential to Juniper Networks.
Best practice Upgrade process
Prepare For Your Next Prelude Upgrade
Continuous Delivery- Complete Guide
Performance Data Collection and Reporting (PDCR)
CPIC at the General Services Administration (GSA)
The Development Process of Web Applications
Upgrade or Re-Implement?
Our New Web Site.
The Use of AMET and Automated Scripts for Model Evaluation
Overview – SOE PatchTT November 2015.
Extend SAP integration
The Right Selective Adoption Strategy for Greater ROI
OpenSAF Developer Days 2008 OpenSAF Release Management Session 15-07
RCM Turbo SQL Version.
Deploying Windows 10 using System Center Configuration Manager
5.0 : Windows Operating System
Chapter 3: The Project Management Process Groups: A Case Study
Market Update.
Windows Server Release Cadence
Ontario Shared Services
Technical update 05 of April 2017
Release Highlights Last Updated for September Monthly Release.
Database SW Releases.
Introduction to CAST Technical Support
November 18 July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Task Group 4e definitions Date.
Market Update for a Buyers Market
SESSION 10.1 Latest developments with TUFMAN
IS&T Project Reviews September 9, 2004.
Tord Glad Nordahl Program Manager - Microsoft
THE REALITY OF USING CONTAINERS TO BUILD PRODUCTS
Protech’s Short and Long Term Roadmap
DIMETRA™ EXPRESS SYSTEM SERVICES
Market Update for a Buyers Market
5/12/2019 2:57 PM © Microsoft Corporation. All rights reserved.
Desktop App Assure Service Microsoft Representative Name June 7, 2019
Proposal on TSC policy for ONAP release Maintenance
Release retrospective
PeopleSoft Test Framework Take changes when you want them with selective adoption Michalynn Koziol July 2019.
Market Update for a Buyers Market
Market Update.
MVD System Modernization Certification Change Request
Presentation transcript:

Agile Evolution - We Heard Your Feedback Current Plan Aug. 2017 – 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 3 + 2 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. * 16.10 and 16.20 are supported for 3 years from their GA dates. © 2018 Teradata © 2018 Teradata

Teradata Database 16.20 Support Plan Teradata Database 16.20 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 16.20.xx.yy 16.20.00 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 16.20 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

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 16.70 releases No dictionary changes Incremental changes through smaller updates reduce risk and testing efforts Feature update 1 Feature update 2 16.20.00 3 years GA In addition to the maintenance releases, Teradata Database 16.20 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 16.70 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

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. 16.20.06) Each update is a cumulative update of previous update releases 16.20.00 16.20.01 16.20.02 16.20.03 16.20.04 16.20.05 16.20.06 16.20.07 16.20.08 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.01, 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

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 16.20 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 16.20.xx version numbering They replace previously planned 16.50, 16.60, and 16.70 releases No dictionary changes during the entire 16.20.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 16.20 will be supported for 3 years from its GA date, plus 2 years of Extended Database Maintenance. After its release, Teradata Database 16.20 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 16.70. These feature updates will be numbered 16.20.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

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 16.20.xx will support all Teradata Database 16.20.XX releases Simpler for customers and partner products: Forward and backward compatible with whole Teradata Database release series Install the latest TTU 16.20.xx version for use with Teradata Database 16.20.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 16.20 will be compatible from 14.10 through 16.20, plus the next 2 database releases. All TTU 16.20.xx releases will support all Teradata Database 16.20xx releases. * Anticipated Teradata Database major release numbers; subject to change © 2018 Teradata © 2018 Teradata

Release Version Numbering Comparison between 16.20 and Pre-16.20 16.20 structure: 16.20.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-16.20 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