From 0fd8c7b7d3516fca16686236252aafb339b97aa9 Mon Sep 17 00:00:00 2001
From: codebien <2103732+codebien@users.noreply.github.com>
Date: Mon, 15 Jan 2024 21:30:06 +0100
Subject: [PATCH 1/2] changelog: data collection update

---
 release notes/v0.49.0.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/release notes/v0.49.0.md b/release notes/v0.49.0.md
index 42286f2121d..e56bcb711ff 100644
--- a/release notes/v0.49.0.md	
+++ b/release notes/v0.49.0.md	
@@ -89,9 +89,10 @@ The migration is straightforward. Just replace `k6/experimental/grpc` with `k6/n
 
 ### Collect usage data on imported internal modules and outputs [#3525](https://github.com/grafana/k6/pull/3525)
 
-// TODO fill with info
-
-
+Added the data collection of the used modules and outputs when the [usage report](https://grafana.com/docs/k6/latest/misc/usage-collection) is enabled. The data collection is only related to the built-in k6 modules and outputs. Private, custom modules and extensions [are never collected](https://github.com/grafana/k6/blob/f35e67902605877ebf2c5e9c8673cd7faf4cdc1e/cmd/report.go#L33-L57). 
+The usage report is enabled by default in k6, but it is possible to opt-out using the [no-usage-report](https://grafana.com/docs/k6/latest/using-k6/k6-options/reference/#no-usage-report) option.
+We always want to improve the product, but at the same time we need to pay attention where we allocate our resources. Having data of what are the most used modules and outputs give us a better confidence to make decisions because we are supported by data.
+It will let us know what is the percentage of our users that will benefit from the introduction of a new feature and on the other side, in case of a breaking change, how many of them would be impacted.
 
 ## UX improvements and enhancements
 

From 95b933371c39e92f57d6980537f265d35c66d4f8 Mon Sep 17 00:00:00 2001
From: codebien <2103732+codebien@users.noreply.github.com>
Date: Tue, 16 Jan 2024 16:00:16 +0100
Subject: [PATCH 2/2] Newline between chapters

---
 release notes/v0.49.0.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/release notes/v0.49.0.md b/release notes/v0.49.0.md
index e56bcb711ff..d11fe6631b7 100644
--- a/release notes/v0.49.0.md	
+++ b/release notes/v0.49.0.md	
@@ -89,8 +89,8 @@ The migration is straightforward. Just replace `k6/experimental/grpc` with `k6/n
 
 ### Collect usage data on imported internal modules and outputs [#3525](https://github.com/grafana/k6/pull/3525)
 
-Added the data collection of the used modules and outputs when the [usage report](https://grafana.com/docs/k6/latest/misc/usage-collection) is enabled. The data collection is only related to the built-in k6 modules and outputs. Private, custom modules and extensions [are never collected](https://github.com/grafana/k6/blob/f35e67902605877ebf2c5e9c8673cd7faf4cdc1e/cmd/report.go#L33-L57). 
-The usage report is enabled by default in k6, but it is possible to opt-out using the [no-usage-report](https://grafana.com/docs/k6/latest/using-k6/k6-options/reference/#no-usage-report) option.
+Added the data collection of the used modules and outputs when the [usage report](https://grafana.com/docs/k6/latest/misc/usage-collection) is enabled. The data collection is only related to the built-in k6 modules and outputs. Private, custom modules and extensions [are never collected](https://github.com/grafana/k6/blob/f35e67902605877ebf2c5e9c8673cd7faf4cdc1e/cmd/report.go#L33-L57). The usage report is enabled by default in k6, but it is possible to opt-out using the [no-usage-report](https://grafana.com/docs/k6/latest/using-k6/k6-options/reference/#no-usage-report) option.
+
 We always want to improve the product, but at the same time we need to pay attention where we allocate our resources. Having data of what are the most used modules and outputs give us a better confidence to make decisions because we are supported by data.
 It will let us know what is the percentage of our users that will benefit from the introduction of a new feature and on the other side, in case of a breaking change, how many of them would be impacted.