copy changelog into docs/releases #5
Conversation
✅ Deploy Preview for silly-marzipan-04567e ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@anasY2 @selectiveduplicate fixed the URL. please take a look |
modified: content/docs/release-notes/cli/2023/23.05.md
|
@robert-s-lee Can we improve the structure a bit? I was thinking along the lines of this: Major release 23.02 (H1 heading)February 10, 2023 (H2 heading)
Patch releases (H2 heading)23.02.01.21 (H3 heading)
I think this displays a more coherent and structured format, using proper heading hierarchy. |
|
sounds good. I propose keeping the major release using the YY.MM.MM.seq format to be consistent with the file and patch format. |
| {{< tabs "ui-docker-download" >}} | ||
| {{< tab "linux/amd64" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230430.1 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< tab "linux/arm64/v8" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230430.1-arm64 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< /tabs >}} No newline at end of file |
There was a problem hiding this comment.
Same suggestions as before for the tabs
| {{< tabs "ui-docker-download" >}} | ||
| {{< tab "linux/amd64" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230630.0 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< tab "linux/arm64/v8" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230630.0-arm64 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< /tabs >}} |
There was a problem hiding this comment.
Same suggestions as before for the tabs
| Arcion New Filter 16k Tables Demo Video | ||
|
|
||
| {{< youtube ydu4f3mjkCo>}} | ||
|
|
||
| Screenshot of all available sources in June 2023 release | ||
|
|
||
|  | ||
|
|
||
| Screenshot of all available targets in June 2023 release | ||
|
|
||
|  | ||
|
|
||
| 1. Pipeline source - SAP ASE (Sybase) | ||
|
|
||
| 1. Pipeline destination - Redis Streams | ||
|
|
||
| 1. Buttons now viewable when scrolling on the webpages | ||
|
|
||
| 1. Can't click save on new Databricks connection when using DBFS | ||
|
|
||
| 1. Can't perform state update on saved-connections | ||
|
|
||
| 1. Filter page timeouts | ||
|
|
||
| 1. Filter update by file not handled properly | ||
|
|
||
| 1. When setting Pertable config for Databricks Lakehouse the schema name is not set into the per table configuration (only catalog name) | ||
|
|
||
| 1. Handle exception when /replication returns 401 | ||
|
|
||
| 1. Allow schema name update when mapping to 2 level db | ||
|
|
||
| 1. Update refresh token behaviour | ||
|
|
||
| 1. UI changes to support SAP ASE (Sybase) as source | ||
|
|
||
| 1. API changes to support SAP ASE (Sybase) as source | ||
|
|
||
| 1. UI changes to support Redis Streams as destination | ||
|
|
||
| 1. API changes to support Redis Streams as destination | ||
|
|
||
| 1. Optimize filter behaviour when rendering a large dataset | ||
|
|
||
| 1. Update replication list header and make columns sortable | ||
|
|
||
| 1. Ability to download all config files | ||
|
|
||
| 1. Handle upload filter containing blocked list in the UI | ||
|
|
||
| 1. Enable PG to PG and MySQL to PG pipeline | ||
|
|
||
| 1. Type 2 CDC support | ||
|
|
||
| 1. MYSQL DDL replication support | ||
|
|
||
| 1. Informix DDL replication support | ||
|
|
||
| 1. Support applier configuration for /dev/null | ||
|
|
||
| 1. Update progress percentage for CHANGE_DATA_CAPTURE phase and TERMINATE replication status | ||
|
|
||
| 1. Reimplement trace log download within replication summary | ||
|
|
||
| ## Patch releases | ||
|
|
||
| ### 23.06.30.1 | ||
|
|
||
| {{< tabs "23.06.30.1" >}} | ||
| {{< tab "linux/amd64" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230630.1 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< tab "linux/arm64/v8" >}} | ||
| ``` | ||
| docker pull arcionlabs/replicant-on-premises:20230630.1-arm64 | ||
| ``` | ||
| {{< /tab >}} | ||
| {{< /tabs >}} |
There was a problem hiding this comment.
Same set of suggestions made in the corresponding Cloud section
|
|
||
| # Major release | ||
|
|
||
| ## 22.08.31.0 |
There was a problem hiding this comment.
If we're specifying dates for the releases, we can consider omitting the year since we're already grouping by year and it's quite apparent imo.
I suggest putting the date inside an appropriate HTML heading, or put it after the version number, followed by a comma. I personally prefer the second approach.
Major release
22.08, September 7
...
There was a problem hiding this comment.
making the date of release in the heading makes it difficult to link release notes by the release number. I would suggesting keeping this as-is for now and figure out another method later.
|
|
||
| 26. Fixed SQLServer fetchObjectIds() function, using schema name to filter tables from SQLServer | ||
|
|
||
| ## Patch release |
2 participants
copy https://www.arcion.io/changelog to docs