Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data files: "dev" folder for next version #144

Closed
markusicu opened this issue Nov 2, 2021 · 2 comments
Closed

data files: "dev" folder for next version #144

markusicu opened this issue Nov 2, 2021 · 2 comments
Assignees

Comments

@markusicu
Copy link
Member

markusicu commented Nov 2, 2021

Discussed in the 2021-nov-01 Unicode Tools meeting.

Going forward, use "dev" folders (e.g., unicodetools/data/ucd/dev) for data files for the next Unicode version, rather than "15.0.0-Update" etc. Only once copy from Unicode 14 folders to "dev". Make all changes in "dev", and when Unicode 15 is released, then copy "dev" to "15.0.0" and similar, and continue developing on "dev" for the then-next Unicode version.

  • The latest data is then always in "dev". This should simplify some scripts and tooling a bit. Data reviewers would always look at the same file paths.
  • It will allow us to have branches for new scripts & characters targeting the "dev" data files, even if they miss a release; we might initially not use this capability.

We would still have a version number for the next version, for printing in data files. We might append suffixes like α or β.

When we first do this, we will need to change the code to look in "dev" first unless the version is an "old" one.


Notify the properties & algorithms group when done / resolve the action in the agenda there (2021-nov-08).

@markusicu markusicu self-assigned this Nov 15, 2021
markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 22, 2021
markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 23, 2021
- add version number 15
- adjust file reading code to detect the next version and read from the "dev" folder
- adjust file writing to omit the version infix
see issue unicode-org#144
markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 23, 2021
markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 23, 2021
- add version number 15
- adjust file reading code to detect the next version and read from the "dev" folder
- adjust file writing to omit the version infix
see issue unicode-org#144
markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 24, 2021
- add version number 15
- adjust file reading code to detect the next version and read from the "dev" folder
- adjust file writing to omit the version infix
- adjust docs
see issue unicode-org#144

also
- change UNICODETOOLS_DIR+data to DATA_DIR
- fix TestSecurity, see issue unicode-org#151
  - fall back from Generated output to input data files
  - CI: no output-to-input symlink
@markusicu
Copy link
Member Author

Starting with Unicode 15, we should use a folder name of .../ucd/15.0.0 instead of .../ucd/15.0.0-Update. (issue #157)

markusicu added a commit to markusicu/unicodetools that referenced this issue Nov 24, 2021
- add version number 15
- adjust file reading code to detect the next version and read from the "dev" folder
- adjust file writing to omit the version infix
- adjust docs
see issue unicode-org#144

also
- change UNICODETOOLS_DIR+data to DATA_DIR
- fix TestSecurity, see issue unicode-org#151
  - fall back from Generated output to input data files
  - CI: no output-to-input symlink
markusicu added a commit that referenced this issue Nov 24, 2021
markusicu added a commit that referenced this issue Nov 24, 2021
- add version number 15
- adjust file reading code to detect the next version and read from the "dev" folder
- adjust file writing to omit the version infix
- adjust docs
see issue #144

also
- change UNICODETOOLS_DIR+data to DATA_DIR
- fix TestSecurity, see issue #151
  - fall back from Generated output to input data files
  - CI: no output-to-input symlink
@markusicu
Copy link
Member Author

Closing this issue now that we have "dev" folders with the latest data, and the tools know to look there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant