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

8259048: (tz) Upgrade time-zone data to tzdata2020f #5

Closed
wants to merge 1 commit into from

Conversation

@kiranoracle
Copy link

@kiranoracle kiranoracle commented Jan 19, 2021

Looking to backport the tzdata2020f changes to jdk16-updates. Changes have passed regression.

JBS: https://bugs.openjdk.java.net/browse/JDK-8259048


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JDK-8259048: (tz) Upgrade time-zone data to tzdata2020f

Download

$ git fetch https://git.openjdk.java.net/jdk16u pull/5/head:pull/5
$ git checkout pull/5

@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Jan 19, 2021

👋 Welcome back kravikumar! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk openjdk bot changed the title Backport fe84ecd52b929759c3f355afc20c5356829351d5 8259048: (tz) Upgrade time-zone data to tzdata2020f Jan 19, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Jan 19, 2021

This backport pull request has now been updated with issue from the original commit.

@openjdk
Copy link

@openjdk openjdk bot commented Jan 19, 2021

@kiranoracle This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8259048: (tz) Upgrade time-zone data to tzdata2020f

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@mlbridge
Copy link

@mlbridge mlbridge bot commented Jan 19, 2021

Webrevs

@kiranoracle
Copy link
Author

@kiranoracle kiranoracle commented Jan 19, 2021

/integrate

@openjdk openjdk bot added the sponsor label Jan 19, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Jan 19, 2021

@kiranoracle
Your change (at version cdff249) is now ready to be sponsored by a Committer.

@coffeys
Copy link
Contributor

@coffeys coffeys commented Jan 19, 2021

/sponsor

@openjdk
Copy link

@openjdk openjdk bot commented Jan 19, 2021

@coffeys @kiranoracle Pushed as commit e72baf1.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants