Final changes moved to autotag template (#295)

* Final changes moved to autotag template

* VCN added

tools/autotag/templates/highlights/6.3.2.md

@@ -0,0 +1,41 @@
+# ROCm 6.3.2 release notes
+
+The release notes provide a summary of notable changes since the previous ROCm release.
+
+- [Release highlights](#release-highlights)
+
+- [Operating system and hardware support changes](#operating-system-and-hardware-support-changes)
+
+- [ROCm components versioning](#rocm-components)
+
+- [Detailed component changes](#detailed-component-changes)
+
+- [ROCm known issues](#rocm-known-issues)
+
+- [ROCm resolved issues](#rocm-resolved-issues)
+
+- [ROCm upcoming changes](#rocm-upcoming-changes)
+
+```{note}
+If you’re using Radeon™ PRO or Radeon GPUs in a workstation setting with a
+display connected, continue to use ROCm 6.2.3. See the [Use ROCm on Radeon GPUs](https://rocm.docs.amd.com/projects/radeon/en/latest/index.html)
+documentation to verify compatibility and system requirements.
+```
+## Release highlights
+
+The following are notable improvements in ROCm 6.3.2. For changes to individual components, see
+[Detailed component changes](#detailed-component-changes).
+
+### ROCm documentation updates
+
+ROCm documentation continues to be updated to provide clearer and more comprehensive guidance for a wider variety of user needs and use cases.
+
+* Documentation about ROCm compatibility with deep learning frameworks has been added. These topics outline ROCm-enabled features for each deep learning framework, key ROCm libraries that can influence the capabilities, validated Docker image tags, and features supported across the available ROCm and framework versions. For more information, see:
+
+    * [PyTorch compatibility](https://rocm.docs.amd.com/en/latest/compatibility/ml-compatibility/pytorch-compatibility.html)
+
+    * [TensorFlow compatibility](https://rocm.docs.amd.com/en/latest/compatibility/ml-compatibility/tensorflow-compatibility.html)
+
+    * [JAX compatibility](https://rocm.docs.amd.com/en/latest/compatibility/ml-compatibility/jax-compatibility.html)
+
+* The [HIP C++ language extensions](https://rocm.docs.amd.com/projects/HIP/en/latest/how-to/hip_cpp_language_extensions.html) and [Kernel language C++ support](https://rocm.docs.amd.com/projects/HIP/en/latest/how-to/kernel_language_cpp_support.html) topics have been reorganized to make them easier to find and review. The topics have also been enhanced with new content.

tools/autotag/templates/known_issues/6.3.2.md

@@ -0,0 +1,4 @@
+## ROCm known issues
+
+ROCm known issues are noted on {fab}`github` [GitHub](https://github.com/ROCm/ROCm/labels/Verified%20Issue). For known
+issues related to individual components, review the [Detailed component changes](#detailed-component-changes).

tools/autotag/templates/resolved_issues/6.3.2.md

@@ -0,0 +1,26 @@
+## ROCm resolved issues
+
+The following are previously known issues resolved in this release. For resolved issues related to
+individual components, review the [Detailed component changes](#detailed-component-changes).
+
+### TransferBench packages not functional
+
+Issue with TransferBench packages not being compiled properly has been fixed. For more information, See [GitHub issue #4081](https://github.com/ROCm/ROCm/issues/4081).
+
+### ROCm Compute Profiler CTest failure in CI
+
+When running the ROCm Compute Profiler (`rocprof-compute`) CTest in the Azure CI environment, the
+`rocprof-compute` execution test failed. This issue was due to an outdated test file that was not renamed
+(`omniperf` to `rocprof-compute`), and the `ROCM_PATH` environment variable not being set in
+the Azure CI environment, resulting in the tool being unable to extract chip information as expected.
+This issue has been fixed in the ROCm 6.3.2 release. See [GitHub issue #4085](https://github.com/ROCm/ROCm/issues/4085).
+
+### MIVisionX memory access fault in Canny edge detection
+
+An issue where Canny edge detection kernels accessed out-of-bounds memory locations while
+computing gradient intensities on edge pixels has been fixed. This issue was isolated to
+Canny-specific use cases on Instinct MI300 series accelerators. See [GitHub issue #4086](https://github.com/ROCm/ROCm/issues/4086).
+
+### AMD VCN instability with rocDecode
+
+A firmware crash on gfx942 devices when AMD Video Core Next (VCN) was used for rocDecode operations has been resolved.

tools/autotag/templates/support/6.3.2.md

@@ -0,0 +1,7 @@
+## Operating system and hardware support changes
+
+ROCm 6.3.2 adds support for Azure Linux 3.0 (kernel: 6.6). Azure Linux is supported only on AMD Instinct accelerators. For more information, see [Azure Linux installation](https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/quick-start.html).
+
+See the [Compatibility
+matrix](https://rocm.docs.amd.com/en/latest/compatibility/compatibility-matrix.html)
+for more information about operating system and hardware compatibility.

tools/autotag/templates/upcoming_changes/6.3.2.md

@@ -0,0 +1,13 @@
+## ROCm upcoming changes
+
+The following changes to the ROCm software stack are anticipated for future releases.
+
+### AMDGPU wavefront size compiler macro deprecation
+
+The `__AMDGCN_WAVEFRONT_SIZE__` macro will be deprecated in an upcoming
+release. It is recommended to remove any use of this macro. For more information, see [AMDGPU
+support](https://rocm.docs.amd.com/projects/llvm-project/en/docs-6.3.2/LLVM/clang/html/AMDGPUSupport.html).
+
+### HIPCC Perl scripts deprecation
+
+The HIPCC Perl scripts (`hipcc.pl` and `hipconfig.pl`) will be removed in an upcoming release.