jdk/jdk repository transitions to Git, GitHub and Skara: September 5
erik.helin at oracle.com
Sat Aug 29 13:43:33 UTC 2020
a reminder that we are now one week away from the jdk/jdk repository 
transition to Git, GitHub and Skara on September 5. As Phil communicated
on the client lists  the plan is still to retire the jdk/client
repository  (please see Phil's e-mail for further details). This
means that on September 4 the following Mercurial repositories will
- jdk/jdk 
- jdk/sandbox 
- jdk/submit 
During the weekend of September 5 - 6 the following Git repositories
will become read-write:
- jdk 
- jdk-sandbox 
As previously communicated, the functionality of the jdk/submit
repository  has been replaced with the /test pull request command
. We have also gotten a few questions in response to the previous
e-mail that we would like to summarize here:
Q: Will the content or the commit hashes of the Git jdk repository 
change during the transition?
A: No, the content and commit hashes of the Git jdk repository are
stable. The "only" thing that will happen during the transition is
that you will be able to create pull requests towards the Git jdk
Q: Can I go ahead and create my personal fork of the jdk repository now?
A: Yes, absolutely! This is a good idea to do prior to Sep 5-6 to make
sure that you can create pull requests once the Git jdk repository is
Q: What happens to patches that are under review at the time of
A: If you have a patch that is under review on Friday Sep 4 then you are
going to have to create a pull request for that patch, even though it
is already under review. "RFR" e-mail threads will *not* be
automatically converted into pull requests.
Q: Will I be able to push directly to the Git jdk repository?
A: No, contributions will be done using pull requests. See the
"Workflow"  section on the Skara wiki for more details.
Q: I'm new to Git and GitHub, do you recommend any resources to get up
A: Yes! Please see the Skara wiki's "Getting Started" guide  that
also has pointers to additional resources for learning more about
Git, GitHub and Skara.
Q: How do I become a member of the OpenJDK group on GitHub?
A: Once you have associated your OpenJDK username and your GitHub
username  you will get an invite via e-mail to join the OpenJDK
group on GitHub .
Q: What if I need some help with getting started on Monday Sep 7?
A: Me and Robin will hang out on IRC in #openjdk on irc.oftc.net.
As always, if you have any questions, feel free to send an e-mail to
skara-dev at openjdk.java.net.
Erik and Robin
On 8/12/20 8:54 AM, Erik Helin wrote:
> Hi all,
> We are now getting closer to the jdk/jdk repository  transitioning to
> Git, GitHub and Skara. JEP 357  and JEP 369  were targeted to JDK
> 16 at the end of May 2020 . It was then also communicated that the
> jdk/jdk repository would transition "early September 2020" .
> The exact target date for the transition of the jdk/jdk repository is
> now set to Saturday September 5, 2020. We aim to complete the transition
> during the weekend of September 5 - 6, 2020. Starting from September 4
> the Mercurial repository for jdk/jdk  will become read-only and the
> Git repository for jdk/jdk  will become read-write on Monday
> September 7.
> If you are an OpenJDK Author, Committer or Reviewer, then please make
> sure you that you are ready for the transition by following the "Getting
> Started" guide on the Skara wiki . In particular, make sure that you
> associate your GitHub username and OpenJDK username, see the "Getting
> Started" guide for details. Feel free to try out the new tools and make
> sure that everything works in the OpenJDK playground repository .
> For those of you doing backports to jdk-updates repositories there is a
> Skara CLI tool, git hg-export, that will export commits from an OpenJDK
> Git repository in a format expected by hg and the OpenJDK Mercurial
> repositories . A "clean" backport of a Git commit looks like the
> $ git clone https://git.openjdk.java.net/jdk
> $ git -C jdk hg-export <REV> | hg -R /path/to/hg/repo import
> As part of transitioning the jdk/jdk repository we will also transition
> the jdk/client repository . There is work ongoing that might result
> in jdk/client being archived instead of transitioned, but that work is
> not guaranteed to be done by September 5. We will send out more details
> on this as we get closer.
> The jdk/submit  repository will not be transitioned, the equivalent
> functionality is provided by the /test pull request command .
> There are continuously updated read-only mirrors of the jdk/jdk ,
> jdk/client  and jdk/sandbox  repositories available if you want
> to create personal forks ahead of the transition. Note that the
> jdk/jdk15  repository will stay on Mercurial as well as the
> jdk-updates/jdk15u  repository (at least for the time being).
> If you have any questions just send an email to skara-dev at openjdk.java.net!
> Erik and Robin
> : https://hg.openjdk.java.net/jdk/jdk
> : https://openjdk.java.net/jeps/357
> : https://openjdk.java.net/jeps/369
> : https://mail.openjdk.java.net/pipermail/jdk-dev/2020-May/004335.html
> : https://mail.openjdk.java.net/pipermail/jdk-dev/2020-May/004322.html
> : https://github.com/openjdk/jdk
> : https://hg.openjdk.java.net/jdk/client
> : https://wiki.openjdk.java.net/display/SKARA/Skara#Skara-GettingStarted
> : https://github.com/openjdk/playground
> : https://wiki.openjdk.java.net/display/SKARA/git-hg-export
> : https://hg.openjdk.java.net/jdk/submit
> : https://github.com/jdk/client
> : https://github.com/jdk/jdk-sandbox
> : https://hg.openjdk.java.net/jdk/jdk15
> : https://hg.openjdk.java.net/jdk-updates/jdk15u
More information about the jdk-dev