Conversation
6182f21 to
68ad9ee
Compare
| - fixed issue when adding a new role, the **Permissions** drop-down list had multiple empty lines at the bottom. Since version 1.5.2. | ||
| - |
There was a problem hiding this comment.
- fixed issue of a new role adding process, when the Permissions drop-down list had multiple empty lines at the bottom.
- пустой дэфис нужен?
There was a problem hiding this comment.
Тут бы еще с заглавной буквы этот пункт списка написать
There was a problem hiding this comment.
Мне кажется, что секции Fixes and compliance updates и Testing improvements можно передвинуть в самый конец страницы.
Т.е. сначала описывать breaking changes (при наличии), затем разделы с фичами релиза или изменением поведения, а затем информацию про фиксы и тесты.
| - unstable health check behavior under partial failures. | ||
| - ``cluster not found`` error when adding or editing cluster settings. | ||
|
|
||
|
|
|
|
||
| |tcm| adds support for TDB workers in the cluster dashboard with integrated health monitoring and visibility. | ||
|
|
||
| Workers are automatically discovered from etcd and continuously monitored via dedicated health check endpoints. |
There was a problem hiding this comment.
discovered from etcd and /then/ continuously monitored
я бы добавил эту связку
| The interface displays workers directly in the stateboard with clear status indicators and a details panel. | ||
| Each worker can be in one of four states: healthy, degraded, unhealthy, or no connection, helping administrators quickly detect and diagnose issues. |
There was a problem hiding this comment.
Если речь в 1м предложении и во 2м об одном и том же определении состояния, то предлагаю назвать его одинаково - state или status.
| The audit log configuration is now safer and more predictable. | ||
|
|
||
| Protocol values are validated during startup. If an invalid protocol is specified, the system automatically falls back to default settings and emits a warning. | ||
| Audit log parameters can be set in advance at the system bootstrap stage by specifying them in the ``auditlog`` field of the initial-settings section in the configuration file. |
| This release introduces support for TDB workers in the cluster dashboard with integrated health monitoring, | ||
| adds TLS configuration guides for secure connections, improves audit log configuration and validation, | ||
| and introduces a feature flag for managing the Tuples tab. It also includes important fixes for LDAP authentication, | ||
| TLS configuration parsing, and a memory leak in SSL cluster connections. |
There was a problem hiding this comment.
фиксы 1.6 ниже перечислены более презентабельно, каждый фикс на отдельной строчке, может и тут так сделать?
| - fixed issue when adding a new role, the **Permissions** drop-down list had multiple empty lines at the bottom. Since version 1.5.2. | ||
| - |
There was a problem hiding this comment.
Тут бы еще с заглавной буквы этот пункт списка написать
| - fixed issue when adding a new role, the **Permissions** drop-down list had multiple empty lines at the bottom. Since version 1.5.2. | ||
| - |
There was a problem hiding this comment.
Мне кажется, что секции Fixes and compliance updates и Testing improvements можно передвинуть в самый конец страницы.
Т.е. сначала описывать breaking changes (при наличии), затем разделы с фичами релиза или изменением поведения, а затем информацию про фиксы и тесты.
| Migration management improvements | ||
| --------------------------------- | ||
|
|
||
| Also, |tcm| 1.5.3 makes migration handling safer and more predictable. |
There was a problem hiding this comment.
Я бы убрала Also
В начале раздела сразу после заголовка выглядит немного странно
(не могу suggestion добавить)
|
|
||
| Latest release in series: 1.6.0 | ||
|
|
||
| This release introduces support for TDB workers in the cluster dashboard with integrated health monitoring, |
There was a problem hiding this comment.
Я бы написала тут полностью первое вхождение названия
Tarantool DataBase (TDB)
| TDB workers monitoring in cluster dashboard | ||
| -------------------------------------------- | ||
|
|
||
| |tcm| adds support for TDB workers in the cluster dashboard with integrated health monitoring and visibility. |
There was a problem hiding this comment.
- Надо добавить ссылку на раздел про воркеры:
https://www.tarantool.io/ru/tarantooldb/doc/latest/examples/tdb_worker/tdb_worker_example/ - нужно написать, что воркеры поддерживаются с версии Tarantool DB 3.1.0.
| TDB workers monitoring in cluster dashboard | ||
| -------------------------------------------- | ||
|
|
||
| |tcm| adds support for TDB workers in the cluster dashboard with integrated health monitoring and visibility. |
There was a problem hiding this comment.
Мы вроде используем нейминг stateboard, и вкладка так тоже называется
Я бы дописала еще, что воркеры отображаются на вкладке Stateboard
| A feature flag has been introduced to control the visibility of the **Tuples** tab in the Explorer interface. | ||
|
|
||
| The tab is displayed only when the corresponding feature flag is enabled and the CRUD module is available. | ||
| The flag can be configured either in the application configuration file or via command-line arguments at startup |
There was a problem hiding this comment.
Тут просится код-блок с настройкой этой фичи
| A feature flag has been introduced to control the visibility of the **Tuples** tab in the Explorer interface. | ||
|
|
||
| The tab is displayed only when the corresponding feature flag is enabled and the CRUD module is available. | ||
| The flag can be configured either in the application configuration file or via command-line arguments at startup |
There was a problem hiding this comment.
Давай напишем в кодблоке, как включить в конфиге TCM опцию:
feature:
tuples: TruePS: меня слегка запутала формулировка application configuration file - у меня сложилось впечатление, что речь идет про приложение в смысле кластер. Я бы так явно и сформулировала, что в конфигурации TCM можно задть
write release notes for