Following discussion in PR #75:

To avoid making too many packages we can possibly have just two packages, we can call the lightweight package as unicode-data-core and bundle everything including unicode-data-core in the all-inclusive unicode-data package.

Currently there are 4 packages depending on unicode-data.

• We should define criteria where to include APIs. As of now, names & scripts are not considered “core”. What about blocks?
• This will require a major version bump.
• What about the existing package unicode-names? If we do not create unicode-data-blocks-scripts, maybe we can deprecate it in favor of the new batteries included unicode-data.

I would propose the following plan:

1. Merge Add support for block and scripts #75.
2. Publish unicode-data-0.3.1 with all changes so far.
3. Update to Unicode 15.0.
4. Publish unicode-data-0.4.0 and names.
5. Rename unicode-data to unicode-data-core.
6. Re-create unicode-data, that re-export all unicode-data-* packages.
7. Publish unicode-data-core-1.0, unicode-data-names-1.0, unicode-data-scripts-1.0 , unicode-data-security-0.1 and unicode-data-1.0.

@harendra-kumar @adithyaov @Bodigrim