Skip to content

Updates for new Japanese calendar era #1979

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

Merged
merged 6 commits into from
Mar 18, 2019
Merged

Conversation

rpetrusha
Copy link

@rpetrusha rpetrusha commented Mar 1, 2019

Updates for new Japanese calendar era

Related to dotnet/samples#686

Contributes to dotnet/docs#10192

Depends on dotnet/docs#10853

//cc @tarekgh

@rpetrusha rpetrusha self-assigned this Mar 1, 2019
@rpetrusha rpetrusha added this to the March 2019 milestone Mar 1, 2019
@rpetrusha rpetrusha added the 🚧 Hold for related PR Indicates a PR can only be merged when other related PRs are merged (see comments for links) label Mar 1, 2019
@@ -1,4 +1,3 @@

> [!IMPORTANT]
> A new era in the <xref:System.Globalization.JapaneseCalendar> and <xref:System.Globalization.JapaneseLunisolarCalendar> begins on May 1, 2019. This change affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://blogs.msdn.microsoft.com/dotnet/2018/11/14/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications on Windows systems to ensure their readiness for the era change.

> A new era in the <xref:System.Globalization.JapaneseCalendar> and <xref:System.Globalization.JapaneseLunisolarCalendar> begins on May 1, 2019. This change affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://blogs.msdn.microsoft.com/dotnet/2018/11/14/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications on Windows systems to ensure their readiness for the era change. See the ["Working with eras"](~/docs/standard/datetime/working-with-calendars.md#working-with-eras) section of the [Working with calendars](~/docs/standard/datetime/working-with-calendars.md) article for additional information and recommendations for using eras in the Japanese calendars.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link (/windows/uwp/design/globalizing/japanese-era-change) looks not working. is this a place holder?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other links looks not working too. I may be missing something but wanted to tell.

Copy link
Author

@rpetrusha rpetrusha Mar 1, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tarekgh, the links work in live builds but not in review builds. Any content that originates outside of the dotnet/docs repo isn't build as part of this PR, so Windows content isn't built.

New examples also aren't included since they still haven't been merged in the dotnet/samples repo.

Copy link
Member

@tarekgh tarekgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the hyperlinks, LGTM

Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM @rpetrusha

You can :shipit: when you merge the associated samples and you get a clean build.

@rpetrusha
Copy link
Author

Closing and reopening to begin new build after dotnet/samples#686 was merged.

@rpetrusha rpetrusha closed this Mar 4, 2019
@rpetrusha rpetrusha reopened this Mar 4, 2019
@mairaw mairaw removed the 🚧 Hold for related PR Indicates a PR can only be merged when other related PRs are merged (see comments for links) label Mar 5, 2019
@rpetrusha rpetrusha added 🚧 Hold for related PR Indicates a PR can only be merged when other related PRs are merged (see comments for links) and removed 🚧 Hold for related PR Indicates a PR can only be merged when other related PRs are merged (see comments for links) labels Mar 8, 2019
@rpetrusha
Copy link
Author

Closing and reopening to begin new build before merge.

@rpetrusha rpetrusha merged commit 8563fb1 into dotnet:master Mar 18, 2019
@rpetrusha rpetrusha deleted the calendar-eras branch March 18, 2019 23:41
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

Successfully merging this pull request may close these issues.

4 participants