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

The update log missed writing #80

Closed
HSSkyBoy opened this issue Sep 4, 2023 · 5 comments
Closed

The update log missed writing #80

HSSkyBoy opened this issue Sep 4, 2023 · 5 comments

Comments

@HSSkyBoy
Copy link
Contributor

HSSkyBoy commented Sep 4, 2023

In Version 3.2.1.1, There are no issues with updating logs. But in version 3.2.1, It seems that there is a repair for both Chinese Simplified and Chinese Traditional, isn't it explicitly stated?

@HSSkyBoy
Copy link
Contributor Author

HSSkyBoy commented Sep 4, 2023

What I mean is that there is no content about Chinese Traditional and Chinese Simplified in the update log at 3.2.1

@Tatsu-syo
Copy link
Owner

Tatsu-syo commented Sep 4, 2023

In 3.2.1, some Simplified Chinese(China) mixed with Traditional Chinese(Taiwan) translations.
I received pull request in @abc0922001 , and I judged it was serious problem for Taiwan users, and decided to release it rapidly, This is reason to release 3.2.1.1.

About release note I can't speak Chinese, I can't update log in Chinese. So, release log is depended on translators.
This is why, there is no content about Chinese Traditional and Chinese Simplified in the update log at 3.2.1.
On Japanese and English release note have content about Chinese Traditional and Chinese Simplified in the update log at 3.2.1.

I must make rules and processes about translation include process.

Example:

  • When coming new translations, make issue for review.
  • If no opinions for some periods、I release it. If some opinions coming I tell opinions for pull request author.
  • If didn't come no release note translation for some periods, release with no release note.

How about? And do you have some ideas?

Sorry for my hurried and poor processes.

@Tatsu-syo
Copy link
Owner

To avoid contamination, I make issue in here .
How about?

@HSSkyBoy
Copy link
Contributor Author

HSSkyBoy commented Sep 6, 2023

No problem

@HSSkyBoy HSSkyBoy closed this as completed Sep 6, 2023
@abc0922001
Copy link
Contributor

To avoid contamination, I make issue in here . How about?

OK

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

3 participants