we missed the quarkus usage feature in 3.2 blog (#1741)

* we missed the quarkus usage feature in 3.2 blog

* Apply suggestions from code review

Co-authored-by: Guillaume Smet <[email protected]>

---------

Co-authored-by: Guillaume Smet <[email protected]>

Author: maxandersen

_posts/2023-07-05-quarkus-3-2-0-final-released.adoc

@@ -17,9 +17,10 @@ Quarkus 3.2 is the first of the link:/blog/lts-releases/[now announced Long Term
 Even if link:/blog/quarkus-2-16-8-final-released/[we will maintain 2.16 for a few months still], we encourage all our users to start their migration journey to Quarkus 3.
 
 Major changes are:
-
+ 
   * Various new security features
   * The ability to test CDI components with `@QuarkusComponentTest`
+  * Build time analytics
 
 Together with improvements in a lot of areas.
 
@@ -33,6 +34,14 @@ Once you upgraded to 3.0, also have a look at the https://github.com/quarkusio/q
 
 == What's new?
 
+=== Build time analytics
+
+To be able to better understand how Quarkus is used, we have added a new build time analytics feature. It is anonymous and opt-in thus fully voluntary.
+
+On first startup of `quarkus dev` you will be asked if you want to share build time analytics with the Quarkus community. If you answer yes, then on `quarkus dev` and builds a small package is sent with information about Java, Maven/Gradle, Quarkus versions, public extensions used, build time, etc. This will help us to better understand how Quarkus is used and what we can improve. If you answer no, then no data is sent.
+
+You can read more on how this works in https://quarkus.io/usage and find more technical details in this https://groups.google.com/g/quarkus-dev/c/Iw17La9pgX[quarkus-dev] post and this https://github.com/quarkusio/quarkus/pull/33555[pull request]. 
+
 === Security
 
 Several new features were added to our security layer making it better than ever: