docs/VictoriaLogs: cut v1.0.0-victorialogs

docs/VictoriaLogs/CHANGELOG.md

@@ -15,6 +15,14 @@ according to [these docs](https://docs.victoriametrics.com/victorialogs/quicksta
 
 ## tip
 
+## [v1.0.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.0.0-victorialogs)
+
+Released at 2024-11-12
+
+This release is identical to [v0.42.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.42.0-victorialogs).
+VictoriaLogs reached production quality since the [initial v0.1.0 release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.1.0-victorialogs) 1.5 years ago,
+so it can be safely used in production.
+
 ## [v0.42.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.42.0-victorialogs)
 
 Released at 2024-11-08

docs/VictoriaLogs/FAQ.md

@@ -11,6 +11,11 @@ aliases:
 - /VictoriaLogs/FAQ.html
 - /VictoriaLogs/faq.html
 ---
+
+## Is VictoriaLogs ready for production use?
+
+Yes. VictoriaLogs is ready for production use starting from [v1.0.0](https://docs.victoriametrics.com/victorialogs/changelog/).
+
 ## What is the difference between VictoriaLogs and Elasticsearch (OpenSearch)?
 
 Both Elasticsearch and VictoriaLogs allow ingesting structured and unstructured logs
@@ -169,4 +174,4 @@ And for the following log, its `_msg` will be `foo bar in body`:
   "message": "",
   "body": "foo bar in body"
 }
-```
+```