RHDEVDOCS-3588: odo 250 release notes

Author: gabriel-rh

cli_reference/developer_cli_odo/odo-release-notes.adoc

@@ -7,78 +7,68 @@ include::modules/common-attributes.adoc[]
 toc::[]
 
 [id="odo-notable-improvements_{context}"]
-== Notable changes and improvements in `{odo-title}`
-
-* `{odo-title}` now supports Devfile v2.
-
-* `odo create -s2i` now converts an S2I component into a devfile component. When running `odo create --s2i <component-type>` `{odo-title}` now creates a converted Devfile component based on the S2I images of the specified component type.
+== Notable changes and improvements in `{odo-title}` version 2.5.0
+
+// #5238
+* Creates unique routes for each component, using `adler32` hashing
+// #5252
+* Supports additional fields in the devfile for assigning resources:
+** cpuRequest
+** cpuLimit
+** memoryRequest
+** memoryLimit
+// #5276
+* Adds the `--deploy` flag to the `odo delete` command, to remove components deployed using the `odo deploy` command: 
 +
-Note that this feature introduces many breaking changes, see xref:../../cli_reference/developer_cli_odo/odo-release-notes.adoc#odo-known-issues_odo-release-notes[Known Issues] to learn more.
-
-* Operator based service is now created on the cluster only after you run `odo push` and not after `odo service create` anymore.
-
-* You can now use the `--container` flag to specify the container you want to attach storage to when running `odo storage create` command. See xref:../../cli_reference/developer_cli_odo/creating_and_deploying_applications_with_odo/working-with-storage.adoc#adding-storage-to-a-specific-container_working-with-storage[Adding storage to a specific container] to learn the details.
-
-* `odo catalog component describe` now returns correct JSON if the same name is used for a component in multiple registries.
+[source,terminal]
+----
+$ odo delete --deploy
+----
+// #5237
+* Adds mapping support to the `odo link` command
+// #5279
+* Supports ephemeral volumes using the `ephemeral` field in `volume` components
+// #5270
+* Sets the default answer to `yes` when asking for telemetry opt-in
+// #5260
+* Improves metrics by sending additional telemetry data to the devfile registry
+// #5287
+* Updates the bootstrap image to `registry.access.redhat.com/ocp-tools-4/odo-init-container-rhel8:1.1.11`
+// #5308 
+* The upstream repository is available at link:https://github.com/redhat-developer/odo[]
 
-* Commands that implement changes directly on a cluster now display a message informing a user that `odo push` is not required.
 
-* When creating a component from a devfile, `odo create` now uses a default component name if the name is not specified.
 
-* `odo` now has Telemetry. See xref:../../cli_reference/developer_cli_odo/understanding-odo.adoc#telemetry-in-odo[Telemetry section] to learn how to modify your Telemetry consent preferences.
+[id="odo-fixed-issues_{context}"]
+== Bug fixes
+// #5294
+* Previously, `odo deploy` would fail if the `.odo/env` file did not exist. The command now creates the `.odo/env` file if required.
+// #5286
+* Previously, interactive component creation using the `odo create` command would fail if disconnect from the cluster. This issue is fixed in the latest release.
 
-*  With `odo service`, you can now add or remove custom resource definitions and `ServiceInstance` information in your devfile.   
- 
 
 [id="odo-getting-support_{context}"]
 == Getting support
 
-.For Documentation
-
-If you find an error or have suggestions for improving the documentation, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *{product-title}* product type and the *Documentation* component type.
-
 .For Product
 
 If you find an error, encounter a bug, or have suggestions for improving the functionality of `{odo-title}`, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose *OpenShift Developer Tools and Services* as a product type and *odo* as a component.
 
 Provide as many details in the issue description as possible.
 
-////
-[id="odo-fixed-issues_{context}"]
-== Fixed issues
-////
-
-[id="odo-known-issues_{context}"]
-== Known issues
-
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760574[Bug 1760574] A deleted namespace is listed in the `odo project get` command.
+.For Documentation
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760586[Bug 1760586] The `odo delete` command starts an infinite loop after a project is deleted and a component name is set.
+If you find an error or have suggestions for improving the documentation, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *{product-title}* product type and the *Documentation* component type.
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760588[Bug 1760588] The `odo service create` command crashes when run in Cygwin.
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760590[Bug 1760590] In Git BASH for Windows, the `odo login -u developer` command does not hide a typed password when requested.
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1783188[Bug 1783188] In a disconnected cluster, the `odo component create` command throws an error `...tag not found...` despite the component being listed in the catalog list.
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1761440[Bug 1761440] It is not possible to create two Services of the same type in one project.
 
-* link:https://bugzilla.redhat.com/show_bug.cgi?id=1821643[Bug 1821643] `odo push` does not work on the .NET component tag 2.1+.
-+
-Workaround: specify your .NET project file by running:
-+
-[source,terminal]
-----
-$ odo config set --env DOTNET_STARTUP_PROJECT=<path_to_your_project>
-----
-
-* When running `odo url create` after `odo create --s2i`, the command fails. `{odo-title}` creates a URL now directly without asking. 
-
-* Wildfly and dotnet S2I components cannot be created with `odo create`.
-
-* `odo env set DebugPort` does not work with converted devfile components. Workaround: use `odo config set --env DEBUG_PORT`.
+////
+[id="odo-known-issues_{context}"]
+== Known issues
 
-* `odo delete --wait` does not wait for the resources to be terminated for devfile components. 
+////
 
 //[id="odo-technology-preview_{context}"]
 //== Technology Preview features `{odo-title}`