Release 1.3.0

[hagenw]

[hagenw]

This is a breaking change release as code that expects a table to be stored as a csv file will break. But as around 99% of use cases will not directly try to access the csv files, but use audb and audformat to access tables, I think it should be fine to go with version 1.3.0 instead of 2.0.0.

[ChristianGeng]

This has a full stop at the end of the sentence. The others do not. What is convention that we are using here?

[hagenw]

The convention is to not use a full stop at the last sentence in an entry. But for earlier ones we use a full stops:

* Added: ``strict`` argument
  to ``audformat.utils.hash()``.
  If set to ``True``,
  the order of the data,
  and its level/column names
  are taken into account
  when calculating the hash

As you can see the last hash has no full stop.

[ChristianGeng]

This looks good to me content-wise.

I have one question about interpuntuation, but that is not a blocker for giving approval.

[ChristianGeng]

This is a breaking change release as code that expects a table to be stored as a csv file will break. But as around 99% of use cases will not directly try to access the csv files, but use audb and audformat to access tables, I think it should be fine to go with version 1.3.0 instead of 2.0.0.

audformat.Database.save and audformat.Table.save are part of the public API and documented. But the gross usage pattern stays intact. So going without a major release is fine.