Skip to content

Commit 1f1ccef

Browse files
anarnold97anarnold97
authored
Merge pull request #804 from anarnold97/mta-1180_mta-7-0-0-rn
MTA-1180: Release notes for v7.0.0
2 parents e748085 + 40bf507 commit 1f1ccef

8 files changed

+254
-20
lines changed

‎docs/release-notes/master.adoc

+7-11
Original file line numberDiff line numberDiff line change
@@ -17,21 +17,17 @@ include::topics/making-open-source-more-inclusive.adoc[]
1717
== Introduction
1818
{ProductName} {DocInfoProductNumber} accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.
1919

20-
These release notes cover all _z_-stream releases of {ProductShortName} 6.2 with the most recent release listed first.
20+
[id="mta-7-0-0"]
21+
== {ProductShortName} 7-0-0
2122

22-
[id="mta-6-2-1"]
23-
== {ProductShortName} 6.2.1
23+
include::topics/mta-rn-new-features-7-0-0.adoc[leveloffset=+2]
2424

25-
include::topics/mta-rn-resolved-issues-6-2-1.adoc[leveloffset=+2]
25+
include::topics/mta-rn-known-issues-7-0-0.adoc[leveloffset=+2]
2626

27-
[id="mta-6-2-0"]
28-
== {ProductShortName} 6.2.0
27+
include::topics/mta-rn-resolved-issues-7-0-0.adoc[leveloffset=+2]
2928

30-
include::topics/mta-rn-new-features-6-2-0.adoc[leveloffset=+2]
31-
32-
include::topics/mta-rn-known-issues-6-2-0.adoc[leveloffset=+2]
33-
34-
include::topics/mta-rn-resolved-issues-6-2-0.adoc[leveloffset=+2]
29+
include::topics/mta-rn-upgrade-notes-7-0-0.adoc[leveloffset=+2]
3530

31+
include::topics/mta-rn-technical-changes-7-0-0.adoc[leveloffset=+2]
3632

3733
:!release-notes:

‎docs/topics/mta-rn-known-issues-7-0-0.adoc

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/release_notes/master.adoc
4+
5+
:_content-type: REFERENCE
6+
[id="rn-known-issues-7-0-0_{context}"]
7+
= Known issues
8+
9+
[ProductFullName] version 7.0.0 has the following issues.
10+
11+
.Pathfinder assessment migration fails on upgrade from {ProductShortName} 6.2.1 to {ProductShortName} 7.0.0
12+
13+
If {ProductShortName} 6.2.1 is installed, when attempting to switch the channel to `stable-7.0`, the operator upgrade succeeds, but a task in the operator pod fails. This failure results in existing pathfinder assessments not being migrated to {ProductShortName} 7.0.0. This bug will be resolved in {ProductShortName} 7.0.1. No assessment data will be lost, it is will simply not be visible in the UI until the release of {ProductShortName} 7.0.1. link:https://issues.redhat.com/browse/MTA-2139[MTA-2139]
14+
15+
.Delayed permission update and user deactivation in `RBAC`
16+
17+
When deleting, deactivating or degrading the role of a user, such as changing the user from `Admin` to `Migrator`, the change can take several minutes to take effect. This delay in changing the user status can pose an operational or security risk. link:https://issues.redhat.com/browse/MTA-1809[MTA-1809]
18+
19+
.Re-enabling Keycloak breaks {ProductShortName}
20+
21+
Keycloak is enabled by default. If you disable and then re-enable Keycloak, you cannot perform any actions in the {ProductShortName} web console after logging in again.
22+
23+
This error is caused as the `credential-mta-rhsso` secret is updated when `auth/Keycloak` is disabled and re-enabled.
24+
25+
The suggested workaround is to restore the old password in the `credential-mta-rhsso` secret, after re-enabling `auth`. link:https://issues.redhat.com/browse/MTA-1152[MTA-1152]
26+
27+
28+
.org.apache.derby.derby dependency not analyzed
29+
30+
The `org.apache.derby.derby` dependency is not analyzed. link:https://issues.redhat.com/browse/MTA-1817[MTA-1817]
31+
32+
.Redundant warning on reassessment of applications with inherited assessments
33+
34+
The system repeatedly shows a warning message about overriding an inherited assessment when reassessing an application.
35+
36+
This warning, appropriate for the first assessment, incorrectly reappears on subsequent reassessments, suggesting that the application is still inheriting its assessment, even after it has been overridden. link:https://issues.redhat.com/browse/MTA-1825[MTA-1825]
37+
38+
For a complete list of all known issues in this release, see the list of link:https://issues.redhat.com/browse/MTA-2060?filter=12428334[Known Issues in Jira].
39+
40+
// using filter - project in (MTA) AND type = Bug AND createdDate >= 2021-01-01 AND createdDate <= 2024-01-30 AND (resolutiondate > 2024-01-30 OR resolutiondate is EMPTY) AND Priority in (Blocker, Critical, Major) ORDER BY priority DESC, key DESC

‎docs/topics/mta-rn-known-issues.adoc

-9
This file was deleted.

‎docs/topics/mta-rn-new-features-7-0-0.adoc

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/release_notes/master.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="rn-new-features-7-0-0_{context}"]
7+
= New features
8+
9+
10+
This section describes the new features and improvements of the {ProductFullName} 7.0.0.
11+
12+
13+
.Enhanced assessment module with custom questionnaire
14+
15+
In {ProductShortName} 7.0.0, the assessment module has been enhanced. The assessment module in this release allows you to import questionnaires using a custom YAML syntax for questionnaire definition.
16+
17+
// add xref
18+
19+
.Grouping applications for assessment into archetypes
20+
21+
In {ProductShortName} 7.0.0, you can assess and analyze entire groups of applications or *archetypes*, according to common characteristics.
22+
23+
Application *archetypes* are defined according to criteria tags and application taxonomy. Each archetype selects how the applications are assessed according to its characteristics.
24+
25+
// For more details, see xref:mta-web-archetypes.adoc[Application archetypes].
26+
27+
28+
.Unlink applications from JIRA
29+
30+
In {ProductShortName} 7.0.0, you now have the ability to unlink an application from a Jira ticket, so that you can manage the links between applications and tickets more effectively. To unlink an application from a Jira ticket, click the `Unlink from Jira` icon in the details view of the application or in the details view of a Migration wave.
31+
32+
// For more details, see xref:mta-web-creating-jira-issues-for-migration-wave.adoc#[Unlink applications from JIRA option].
33+
34+
.YAML syntax for new rules
35+
36+
New rules that use YAML syntax to support metadata, `message` and `tag` actions, rule conditions, provider conditions for *Java* and *Go* providers, and other file tagging and characteristics.
37+
38+
39+
.Dynamic reports
40+
41+
{ProductShortName} 7.0.0 produces dynamic analysis reports that collect aggregated issues and dependencies across the application portfolio. They identify portfolio-wide trends, drill down to specific lines in source code, and fully integrate with {ProductShortName} User Interface (UI).
42+
43+
.Multi-language analysis
44+
45+
{ProductShortName} 7.0.0 supports migrating applications written in Java and Golang implemented in Language Server Protocol (LSP).
46+
47+
:FeatureName: Multi-language analysis for Golang
48+
include::technology-preview.adoc[]
49+
50+
51+
52+
53+

‎docs/topics/mta-rn-resolved-issues-7-0-0.adoc

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/release_notes-7.0/master.adoc
4+
5+
:_content-type: REFERENCE
6+
[id="mta-rn-resolved-issues-7-0-0_{context}"]
7+
= Resolved issues
8+
9+
The following highlighted issues have been resolved in {ProductFullName} version 7.0.0.
10+
11+
.No update notification after editing fields
12+
13+
In previous versions of {ProductShortName}, no `Update Notification` appeared at top of window after the fields `Application`, `Job Function`, and `Business services` were updated. This issue has been resolved in {ProductShortName}. link:https://issues.redhat.com/browse/MTA-1024[MTA-1024]
14+
15+
.Not possible to create a Jira instance behind a proxy
16+
17+
In previous versions of {ProductShortName}, it was not possible to create a Jira instance (issues.stage.redhat.com) behind a proxy. This issue has been resolved in {ProductShortName}. link:https://issues.redhat.com/browse/MTA-849[MTA-849]
18+
19+
// think we are safe to move this
20+
.CVE-2023-6291: A flaw was found in the `redirect_uri validation` logic
21+
22+
A flaw was found in the `redirect_uri validation` logic that allows for a bypass of otherwise explicitly allowed hosts. The problem arises in the `verifyRedirectUri` method, which attempts to enforce rules on `user-controllable` input, but can cause a desynchronization in how Keycloak and browsers interpret URLs.
23+
24+
For more details, see link:https://access.redhat.com/security/cve/cve-2023-6291[(CVE-2023-6291)].
25+
26+
For a complete list of all issues resolved in this release, see the list of link:https://issues.redhat.com/issues/?filter=12420807[Resolved Issues in Jira].
27+

‎docs/topics/mta-rn-technical-changes-7-0-0.adoc

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/release_notes-7.0/master.adoc
4+
5+
:_content-type: REFERENCE
6+
[id="mta-rn-technical-changes-7-0-0_{context}"]
7+
= Technical changes
8+
9+
The following technical changes have been made in {ProductFullName} 7.0.0:
10+
11+
* The Maven Plugin has been deprecated.
12+
13+
* Language Server Protocol (LSP) Analyzer change.
14+
15+
[id="mta-rn-technical-changes-rules-7-0-0_{context}"]
16+
== Rules
17+
18+
.Rules can only be written in YAML
19+
20+
Rules written in Groovy and Java are discontinued in {ProductShortName} version 7.0.0. Some of the previous Groovy Java rules have been converted to YAML rules wherever possible.
21+
22+
An important modification to the rule's engine is that it is no longer possible to query anything apart from the tags stored within the engine's internal data structures. This means that all the features that were enabled by using the `graph-query` element in the rule are no longer available.
23+
24+
.Java Class child elements not supported in {ProductShortName}
25+
26+
The Java Class child elements `annotation-list`, `annotation-type` and `annotation-literal` are not supported in {ProductShortName} version 7.0.0.
27+
28+
.Elements <project> and <dependency> are merged into one dependency condition
29+
30+
The capabilities of <project> and <dependency> elements in the old syntax are merged into one dependency condition in the new rules syntax.
31+
32+
.Transformation capabilities of `xslt` element are discontinued
33+
34+
XML transformation capabilities offered by the `xslt` element are discontinued.
35+
36+
.Explicit `iteration` element is discontinued
37+
38+
The explicit `iteration` element is discontinued in {ProductShortName} version 7.0.0.. If a condition returns a list of items via the `as` construct, iteration is implied.
39+
40+
.Test rules not supported in the current version
41+
42+
Test rules are not supported in {ProductShortName} version 7.0.0.
43+
44+
.Overriding a rule discontinued
45+
46+
Overriding a rule is discontinued in {ProductShortName} version 7.0.0.
47+
48+
.Creating custom rule categories discontinued
49+
50+
Creating custom rule categories is discontinued in {ProductShortName} version 7.0.0.
51+
52+
.Information and optional categories of rules are discontinued.
53+
54+
In {ProductShortName} version 7.0.0, any previous rules of information and optional categories will only create technology tags.
55+
56+
.Java analysis capabilities
57+
58+
In {ProductShortName} version 7.0.0, the following Java analysis capabilities have been deprecated:
59+
60+
* Ability to match on specific arguments of a Java method constructor is not supported in the current version
61+
62+
* Matching Java references from JavaServer Pages (JSP) files are not supported in the current version
63+
64+
* `Mavenizing` a Java project, meaning write a POM and possibly move code around so that it builds in Maven, is discontinued.
65+
66+
.Analysis report changes
67+
68+
The following functionality in Analysis reports has been deprecated:
69+
70+
* Story points are shown as integers. The “level of effort” view and their mappings are deprecated in {ProductShortName} version 7.0.0.
71+
72+
* Transactions reports are deprecated in {ProductShortName} version 7.0.0.
73+
74+
* The view for “Archives shared by multiple applications” is deprecated in {ProductShortName} version 7.0.0.
75+
76+
* The view for “Review rule providers execution overview” deprecated in {ProductShortName} version 7.0.0.

‎docs/topics/mta-rn-upgrade-notes-7-0-0.adoc

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/release_notes-7.0/master.adoc
4+
5+
:_content-type: REFERENCE
6+
[id="mta-rn-upgrade-notes-7-0-0_{context}"]
7+
= Upgrade notes
8+
9+
The following are upgrade notes for {ProductFullName}
10+
11+
.Hub database volume size
12+
13+
In version 7.0.0 of {ProductShortName}, the default size of the hub database volume has been increased to 10GiB.
14+
15+
If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.0 will result in a failure due to the operator trying to change the volume size from 5GiB to 10G.
16+
17+
To avoid this issue, you can directly set the volume size by setting:
18+
19+
// the example said 5Gi but should it be 10Gi
20+
[source,yaml]
21+
----
22+
...
23+
hub_database_volume_size: 10Gi
24+
...
25+
----
26+
27+
By doing this, you will avoid the operator trying to resize the volume.
28+
29+
30+
.Existing data
31+
32+
When upgrading to {ProductShortName} 7.0.0, all existing data will be retained, except for individual analysis reports for applications.
33+
34+
As both the analysis and reporting engines have been replaced with this version, you will be required to conduct a re-run of the analysis in order to obtain data on issues and dependencies.
35+
36+
37+
.Version upgrade
38+
39+
You can upgrade to {ProductShortName} 7.0.0 from 6.2.1. It is not recommended to pursue any alternative upgrade route. If you wish to upgrade from a previous version, it is recommended to proceed in a sequential manner until you finally upgrade from {ProductShortName} version 6.2.1 to 7.0.0.

‎docs/topics/technology-preview.adoc

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
// When including this file, ensure that {FeatureName} is set immediately before
2+
// the include. Otherwise it will result in an incorrect replacement.
3+
4+
[IMPORTANT]
5+
====
6+
[subs="attributes+"]
7+
{FeatureName} is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
8+
9+
For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
10+
====
11+
// Undefine {FeatureName} attribute, so that any mistakes are easily spotted
12+
:!FeatureName:

0 commit comments

Comments
 (0)