Preceden

EC Release 12.2 v1.0

Again, attempting to compress the hardening due to higher trust in automation and leveraging Flyway implementation.

EC-12.2

Finishing Installation script

November 5, 2019 - November 8, 2019

Upgrade team to finish Installation script for TC2

Scope Work Done

November 14, 2019

No more planned changes to be made to the product. Only critical/blocker bug fixes and security fixes are allowed, as part of hardening.

Any changes needed for the release is made in DEFAULT, and only merged to RELEASE branch upon GREEN build.

Pre TC1 Code Freeze / Tag RC0

November 14, 2019

No more planned changes to be made to the product. Only new bugfixes and security fixes are allowed, as part of hardening.

RC0 Tag: First test cycle env. (plain), and basis for Upgrade Script.

TC1 Env prep

November 15, 2019 - November 21, 2019

  • Prepare environments for TC1
  • Based on the requirements defined in Configuration Management for a minor release
  • TC1 will only hold upgraded EC-12.2 Release Candidate envs.
  • Bug Quest envs prepare

RC0 ready morning 13th Nov
BQ env from Flyway scripts ("plain") ready by 14th.
Upgrade script: 3d from RC0, Friday 15th
Docker images with base version ready before 15th.
CM deploying envs based on upgraded dockers from Monday 18th
Start TC1 from Wed 20th.

Upgrade script preparation

November 15, 2019 - November 19, 2019

Online Help Review

November 19, 2019 - December 13, 2019

  • Review Online Help that was modified or added for 12.2
  • If applicable, complete review of FULL Online Help from 12.1-SP01
  • What to review: BF Descriptions, screenshots, inline images, bad characters, layout, etc
  • Refer ECPTs of Online Help review by each teams.
  • Complete DB related changes before Pre-TC2 DB Code Freeze
  • Generate Offline version PDF, and share with EC Support for review.

Customer Upgrade Script testing

November 20, 2019 - November 28, 2019

Connect with 2-3 customer projects with EC-12.1-SP01 systems that can be used to test installation of 12.2 upgrade script.

Ownership to be placed with Upgrade team.

Bug Quest 1

November 21, 2019 - 1 day

Exploratory testing, for all PRD and PRS who can participate.
Upgraded 12.2.RC0 environment.

TC1

November 22, 2019 - November 27, 2019

Testing on Upgrade environment

Manual testing:
- Execution of all the ECPTs related to the planned scope
- Critical regression tests (not yet automated)

Automated Tests (ALL)

TC1 Bugfixing

November 22, 2019 - November 28, 2019

Fixing bugs found during TC1, or critical/blocker bugs accepted passed the Scope Work Done point.

Installation Test

November 22, 2019 - November 27, 2019

Pre TC2 FULL Code Freeze / Tag RC

November 28, 2019

  • Code Freeze @ 14:00 CET

Pre TC2 DB Code Freeze / Tag RC

November 28, 2019

Allow for Upgrade team to incorporate the db changes into the upgrade script that will be used for TC2

TC2 Env prep (3d)

November 29, 2019 - December 3, 2019

  • Prepare base environments
  • Upgrade all base environments
  • Prepare plain environment
  • Requirements for Cluster / SSO / RR?

Ready by morning KL next day.

Upgrade script preparation TC2

November 29, 2019 - December 2, 2019

Test EC SDK, Assembly Tools

November 29, 2019 - December 5, 2019

FRMW Team, Testers need to test the EC Tools: EC SDK, EC Assembly tool.

TC2 (4d)

December 4, 2019 - December 9, 2019

Manual testing:
- ALL not-yet-automated Regression Tests
- Failed and Fixed issues in TC1
- Test blocked/NA/not completed in TC1
- (N/A) Retest scope issues having db upgrade impact area info in JIRA
- Exploratory Testing of key functional areas

Automated testing (ALL):
- Functional UI regression/scenarios tests
- Functional Issue tests
- Screen/Smoke tests (IUD)
- Performance tests
- Security (Veracode Scan)
- Scenario Tester (Revenue)
- Run automated regression tests on Imported DB

Scope:
- Testing on Upgrade environment
- Manual Test Execution on Upgrade and Plain Environment

TC2 Bugfixing

December 4, 2019 - December 10, 2019

Fixing bugs found in TC2

TC2 Bug Quest

December 5, 2019 - 1 day

Second Bug Quest, on an Upgraded environment

Final Code Freeze / Tag RC

December 10, 2019

  • Code Freeze @ 14:00 CET
  • Create last release candidate

Documentation Finalization

December 11, 2019 - December 17, 2019

Final review and generation of PDFs

UAT Env prep (3d)

December 11, 2019 - December 13, 2019

  • Prepare base environments
  • Upgrade script amendments from TC2 bugfixes
  • Upgrade all base environments
  • Prepare plain environments

Upgrade script preparation Final

December 11, 2019 - December 12, 2019

BVT (2d)

December 16, 2019 - 4 days

@until 11am CET
Last test cycle, based on final RC, validating blocker fixes from TC2.

UAT by PO/PM (2d)

December 16, 2019 - 4 days

@until 11am CET
Exploratory Testing of Critical Path scenarios, sign-off that all key features work as expected.

G/N-G Decision

December 19, 2019

@11am CET

RELEASE!

December 20, 2019

Our goal is to release as short as possible after the GO/NO-GO decision.

Documentation

How to Upgrade verification (4 days)

November 11, 2019 - November 15, 2019

Out of scope:
"Product area specific upgrade impact" section

Verification by Upgrade Team and Release Team.

How to Upgrade document:
http://ecpedia.eu.tieto.com/display/RD121/How+to+Upgrade+from+EC-12.1

Documentation Scope:
http://ecpedia.eu.tieto.com/display/RE121/EC-12.1-SP01+Documentation+Scope

Installation Guide verification (4 days)

November 11, 2019 - November 14, 2019

  • Verification by Erik, Framework Team, and CM Team.

Installation Guide document:
http://ecpedia.eu.tieto.com/display/RD122/EC-12.2+-+Installation+Guide

Documentation Scope:
http://ecpedia.eu.tieto.com/display/RE121/EC-12.1-SP01+Documentation+Scope

ECSRs verification

November 18, 2019 - December 5, 2019

  • Verification by Product Support Team.
  • Release Team prepares the list of ECSRs in Excel sheet.
  • 15th Nov: Release Team send an email to Product Support Team to verify ECSRs - attach the Excel file to email.

RN Details verification in JIRA filters

November 18, 2019 - December 5, 2019

  • JIRA filters of each product areas will be provided.
  • POs will verify JIRAs having labels rn-exclude, Task, online-help
  • 15th Nov: Release Team send an email to all POs to verify ECPDs in JIRAs

Release Details document: http://ecpedia.eu.tieto.com/display/RD122/EC-12.2+-+JIRA+Filters+for+Release+Details

Documentation Scope:
http://ecpedia.eu.tieto.com/display/RE122/EC-12.2+Documentation+Scope

Offline Help generation (BQ1 env)

November 21, 2019

Responsibility: Release Team to generate the Offline Help:
- PDFs BF Documents
- HTML version
Offline Help to be generated in Bug Quest 1 env (EC screen).
All product teams need to verify the Offline Help (BF documents) throughout TC1 and TC2.

Offline Help generation (BQ2 env)

December 5, 2019

Responsibility: Release Team to generate the Offline Help:
- PDFs BF Documents
- HTML version
Offline Help to be generated in Bug Quest 2 or TC2 env (EC screen).
Fixes of Offline Help in TC1 will be available in TC2 Offline Help.
All product teams need to verify the Offline Help (BF documents) throughout TC1 and TC2.

Due Date for preparation of Known Limitations

December 6, 2019

Preparation and verification by POs & PMs.

Known Limitations (in the Release Notes):
http://ecpedia.eu.tieto.com/display/RD121/EC-12.1-SP01+-+Release+Notes#EC-12.1-SP01-ReleaseNotes-KnownLimitations

Upgrade Impact verification (3 days)

December 6, 2019 - December 10, 2019

  • Verification by POs.
  • Upgrade Team need to verify that the upgrade scripts mentioned in Upgrade Impact document are included in release artifacts.

Upgrade Impact section in HowTo Upgrade document:
http://ecpedia.eu.tieto.com/display/RD121/How+to+Upgrade+from+EC-12.1

Release Details final verification in ECpedia (2 days)

December 9, 2019 - December 10, 2019

Responsibility: POs and Release Team (final verification)

Release Details document: http://ecpedia.eu.tieto.com/display/RD122/EC-12.2+-+JIRA+Filters+for+Release+Details

Documentation Scope:
http://ecpedia.eu.tieto.com/display/RE122/EC-12.2+Documentation+Scope

Refine release scope into Highlights in Release Notes (5 days)

December 9, 2019 - December 13, 2019

Highlights document (in the Release Notes):
http://ecpedia.eu.tieto.com/display/RD122/EC-12.2+-+Release+Notes

Content refinement from Release Scope page:
http://ecpedia.eu.tieto.com/display/RE122/EC-12.2+Release+Scope

Responsibility: Release Team

Due Date for modifications of Technical Overview

December 11, 2019

Preparation, modifications and verification by POs & PMs.

Technical Overview document:
http://ecpedia.eu.tieto.com/display/RD122/EC-12.2+-+Technical+Overview

Documentation Scope:
http://ecpedia.eu.tieto.com/display/RE122/EC-12.2+Documentation+Scope

RN Details Beautification (5 days)

December 11, 2019 - December 17, 2019

  • Release Team extracts all RN Details from JIRA into ECpedia.
  • Release Team sends an email with the RN Details in Word document to Marketing Team for beautification.

Offline Help generation (Final - BVT)

December 16, 2019

Responsibility: Release Team to generate the Offline Help:
- PDFs BF Documents
- HTML version
Teams need to review again the affected Offline Help (which was fixed in TC2)
Release Team briefly scan through the final Offline Help before upload to ECUC.

Test Online Help installation

December 16, 2019

  • Test Online Help screenshots installation by Release Team.
  • Online Help artifact is provided by CM Team.

Public Holidays