#610 update the release:prepare phase only validates the package and necessary information

Author: csun-cpointe

DRAFT_RELEASE_NOTES.md

@@ -16,6 +16,7 @@ _Note: instructions for adapting to these changes are outlined in the upgrade in
   - The `foundation-data-access` Java module
 - PySpark will no longer throw an exception when a required field is `None` but instead filter it out. See Changes in Spark/PySpark Schema Behavior below for more details.
 - Spark/PySpark will no longer filter out records with `null`/`None` fields that are not required and have validation. See Changes in Spark/PySpark Schema Behavior below for more details.
+- The default `preparationGoals` for the release plugin had been changed to `clean validate` to shorten the release preparation time.
 
 ## aiSSEMBLE-Vault Docker Image
 The aiSSEMBLE-vault docker image will no longer be available. We also remove the related `vault-deploy` profile.

pom.xml

@@ -310,19 +310,10 @@
                     <artifactId>maven-release-plugin</artifactId>
                     <configuration>
                         <scmCommentPrefix>:bookmark: [maven-release-plugin] </scmCommentPrefix>
-                        <!-- The helm charts can't be built at all once the version changes unless they are being
-                          released.  Many charts depend on other charts, and so cannot be packaged properly unless those
-                          dependencies are already available in the helm repo. !!WARNING!! though it seems that we should
-                          just be using preparationProfiles, unfortunately this adds the enabled profiles to the
-                          release.properties file that the plugin uses to track settings.  This file is required to run
-                          the release:perform goal, but will always allow preparationProfiles to bleed into the perform
-                          step.  So if we do this naively, it ends up skipping the helm modules during release so the
-                          charts aren't published.  We could add a "un-skip-helm" profile that's enabled by
-                          releaseProfiles, but that seemed worse than simply using the goals config property to bypass
-                          updating the activate profiles of release.properties.
-
-                          Also add pyproject.toml changes to git (see below)-->
-                        <preparationGoals>clean install scm:add -Pskip-helm</preparationGoals>
+                        <!-- the CI build already compile and verify all the packages so to shorten the release:prepare time
+                             we can just validate the packages and necessary information. Also, this can also prevent the
+                             docker builder being created in the release prepare time -->
+                        <preparationGoals>clean validate</preparationGoals>
 
                         <!-- Because the release plugin doesn't build after updating to the next development snapshot,
                           the habushu-managed updates to pyproject.toml files lags behind. To prevent the first