3.0 whats new #3960

andreyaksenov · 2023-12-22T08:19:54Z

Staging:

TODO: update the release date in two documents if the release is postponed.

P.S. Didn't update the SVG that visualizes the release calendar. Let's think about its benefits. IMO, multidimensional pivot tables with colored cells are hard to read. Looks like the regular table might be scanned much quicker. Moreover, it's hard to maintain this SVG. I'd also squash patch versions in the Release lifetime table into one line:

version: shows the latest patch version (for example, 3.0.3) and leads to the 3.0 what's new page, which includes links to all GitHub releases.
Release: shows the release date for this patch release, not the major release date. The major release date is shown on the 3.0 what's new page.
End of life: shows the end of life date for the major release series. So, we shouldn't repeat the same date for each patch release.

p7nov

LGTM, just some suggestion with wording improvements.

p7nov · 2023-12-26T09:12:52Z

doc/release/3.0.0.rst

May use just 3.0 as a name? We don't create separate pages for minor releases anymore, so this page is also for all 3.0.x versions.

p7nov · 2023-12-26T09:13:34Z

doc/release/3.0.0.rst

+Releases on GitHub: :tarantool-release:`3.0.0`
+
+The 3.0 release of Tarantool introduces a new declarative approach for configuring a cluster,
+a visual tool for managing, configuring, and monitoring Tarantool EE clusters,


Suggested change

a visual tool for managing, configuring, and monitoring Tarantool EE clusters,

a new visual tool -- Tarantool Cluster Manager,

p7nov · 2023-12-26T09:15:29Z

doc/release/3.0.0.rst

+-----------------------------
+
+Starting with the 3.0 version, Tarantool provides the ability to :ref:`configure the full topology of a cluster <configuration>` using a declarative YAML configuration instead of configuring each instance using a dedicated Lua script.
+Using a new approach, you can use local configuration in a YAML file for each instance or store configuration data in one reliable place, for example, a Tarantool or an etcd cluster.


There are four words use/using in two sentences, better to rephrase

Suggested change

Using a new approach, you can use local configuration in a YAML file for each instance or store configuration data in one reliable place, for example, a Tarantool or an etcd cluster.

With a new approach, you can write a local configuration in a YAML file for each instance or store configuration data in one reliable place, for example, a Tarantool or an etcd cluster.

p7nov · 2023-12-26T09:18:41Z

doc/release/3.0.0.rst

+       • Starting an instance [sharded_cluster:storage-b-001]...
+       • Starting an instance [sharded_cluster:storage-b-002]...
+       • Starting an instance [sharded_cluster:router-a-001]...
+


I find "Learn more in <>" sentences in the end of what's new sections more helpful than just links under some words in descriptions. Anyway this is minor, up to you.

I'd keep this as is because Learn more phrases distract a user from scanning a what's new. But this definitely works better for regular topics.

p7nov · 2023-12-26T09:20:39Z

doc/release/3.0.0.rst

+Database statistics
+~~~~~~~~~~~~~~~~~~~
+
+Starting with 3.0, Tarantool provides extended statistics about memory consumption for the given space or even specific tuples.


This is a long document, so I prefer avoiding needless words.

Suggested change

Starting with 3.0, Tarantool provides extended statistics about memory consumption for the given space or even specific tuples.

Starting with 3.0, Tarantool provides extended statistics about memory consumption for the given space or specific tuples.

p7nov · 2023-12-26T09:52:05Z

doc/release/3.0.0.rst

+New DEB and RPM packages
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+With this release, the approach to delivering Tarantool to end users using DEB and RPM packages is slightly revised.


Suggested change

With this release, the approach to delivering Tarantool to end users using DEB and RPM packages is slightly revised.

With this release, the approach to delivering Tarantool to end users in DEB and RPM packages is slightly revised.

p7nov · 2023-12-26T09:52:59Z

doc/release/3.0.0.rst

+varbinary in Lua
+~~~~~~~~~~~~~~~~
+
+In the previous versions, Tarantool already supported a ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.


Suggested change

In the previous versions, Tarantool already supported a ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.

In the previous versions, Tarantool already supported the ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.

p7nov · 2023-12-26T09:53:36Z

doc/release/3.0.0.rst

+~~~~~~~~~~~~~~~~
+
+In the previous versions, Tarantool already supported a ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.
+But working with ``varbinary`` database fields required using various workarounds, for example, using C to process such data.


Suggested change

But working with ``varbinary`` database fields required using various workarounds, for example, using C to process such data.

But working with ``varbinary`` database fields required workarounds, such as using C to process such data.

p7nov · 2023-12-26T09:55:33Z

doc/release/3.0.0.rst

+-   :ref:`Read views <2-11-read_views>` are in-memory snapshots of the entire database that aren't affected by future data modifications.
+-   :ref:`Pagination <2-11-pagination>` for getting data in chunks.
+
+With this release, a read view object supports the ``after`` and ``fetch_pos`` arguments for the ``select`` and ``pairs`` methods:


Suggested change

With this release, a read view object supports the ``after`` and ``fetch_pos`` arguments for the ``select`` and ``pairs`` methods:

With the 3.0 release, a read view object supports the ``after`` and ``fetch_pos`` arguments for the ``select`` and ``pairs`` methods:

p7nov · 2023-12-26T09:57:24Z

doc/release/3.0.0.rst

+IPROTO tuple format
+~~~~~~~~~~~~~~~~~~~
+
+Starting with the 3.0 version, the IPROTO protocol is extended to support for sending names of tuple fields in the :ref:`IPROTO_CALL <box_protocol-call>` and other IPROTO responses.


"protocol is extended to support for" sounds too complex. Perhaps there is a simpler wording for this.

andreyaksenov changed the base branch from latest to 3.0 December 22, 2023 08:20

andreyaksenov linked an issue Dec 22, 2023 that may be closed by this pull request

3.0 release notes #3517

Closed

4 tasks

andreyaksenov force-pushed the 3.0-whats-new branch 28 times, most recently from 0acfd88 to 81d5c8a Compare December 25, 2023 13:28

andreyaksenov force-pushed the 3.0-whats-new branch 5 times, most recently from 2d99715 to 06274a4 Compare December 25, 2023 14:36

andreyaksenov requested a review from p7nov December 25, 2023 14:50

andreyaksenov force-pushed the 3.0-whats-new branch 2 times, most recently from a65d9c0 to fff5b05 Compare December 25, 2023 15:46

3.0 what's new

e3bf9cf

andreyaksenov force-pushed the 3.0-whats-new branch from fff5b05 to e3bf9cf Compare December 25, 2023 15:51

andreyaksenov added 3 commits December 26, 2023 10:09

3.0 what's new - fix indentation

225bf5f

3.0 what's new - update release date

dc6e5ef

3.0 what's new - update per review

52d5595

andreyaksenov force-pushed the 3.0-whats-new branch 2 times, most recently from 33c0500 to 4e92c61 Compare December 26, 2023 07:39

andreyaksenov added 2 commits December 26, 2023 10:41

3.0 what's new - update intro

dee434d

3.0 what's new - move the 'flight recorder' section

77fdd45

andreyaksenov force-pushed the 3.0-whats-new branch from 4e92c61 to 77fdd45 Compare December 26, 2023 07:41

3.0 what's new - add links

9b4a482

p7nov approved these changes Dec 26, 2023

View reviewed changes

andreyaksenov added 2 commits December 26, 2023 13:12

3.0 what's new - update per review 2

49d3318

3.0 what's new - add TCM images

9bd83d1

andreyaksenov force-pushed the 3.0-whats-new branch from 22cb535 to 9bd83d1 Compare December 26, 2023 10:34

andreyaksenov merged commit 34ff4cd into 3.0 Dec 26, 2023
1 check failed

andreyaksenov deleted the 3.0-whats-new branch December 26, 2023 10:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

3.0 whats new #3960

3.0 whats new #3960

andreyaksenov commented Dec 22, 2023 •

edited

Loading

p7nov left a comment

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

andreyaksenov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

p7nov Dec 26, 2023

	a visual tool for managing, configuring, and monitoring Tarantool EE clusters,
	a new visual tool -- Tarantool Cluster Manager,

	Using a new approach, you can use local configuration in a YAML file for each instance or store configuration data in one reliable place, for example, a Tarantool or an etcd cluster.
	With a new approach, you can write a local configuration in a YAML file for each instance or store configuration data in one reliable place, for example, a Tarantool or an etcd cluster.

	Starting with 3.0, Tarantool provides extended statistics about memory consumption for the given space or even specific tuples.
	Starting with 3.0, Tarantool provides extended statistics about memory consumption for the given space or specific tuples.

	With this release, the approach to delivering Tarantool to end users using DEB and RPM packages is slightly revised.
	With this release, the approach to delivering Tarantool to end users in DEB and RPM packages is slightly revised.

	In the previous versions, Tarantool already supported a ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.
	In the previous versions, Tarantool already supported the ``varbinary`` type for :ref:`storing data <index_box_field_type_details>`.

	But working with ``varbinary`` database fields required using various workarounds, for example, using C to process such data.
	But working with ``varbinary`` database fields required workarounds, such as using C to process such data.

	With this release, a read view object supports the ``after`` and ``fetch_pos`` arguments for the ``select`` and ``pairs`` methods:
	With the 3.0 release, a read view object supports the ``after`` and ``fetch_pos`` arguments for the ``select`` and ``pairs`` methods:

3.0 whats new #3960

3.0 whats new #3960

Conversation

andreyaksenov commented Dec 22, 2023 • edited Loading

p7nov left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

andreyaksenov commented Dec 22, 2023 •

edited

Loading