Project Panama is moving to GitHub

Jorn Vernee jorn.vernee at
Tue Jan 14 14:58:31 UTC 2020

Hi all,

You might have heard that there is an OpenJDK project named Skara 
evaluating and trialing using Git for OpenJDK and GitHub for hosting the 
repositories [1]. We have been asked to try out Git, GitHub and the 
Skara tooling, as a means of validating, and to provide feedback about 
the Project Skara effort. There is already a number of OpenJDK projects 
using Git, GitHub and Skara:
- OpenJFX
- OpenJMC
- Loom
- Mobile
- Skara

A transition entails switching to Git as an SCM (see the Git manual 
[2]), and the repository would be hosted on GitHub [3]. After the 
transition, the current Mercurial repository would no longer be updated. 
There is currently already a read-only mirror in place [4], which you 
can use to try out Git and some of the tooling, though submitting pull 
requests and pushing there are currently not supported.

I suggest that project Panama transition to git, GitHub and Skara and 
that we set the target date for the transition to around 2 weeks from 
now. For example Monday the 27th of January, or otherwise later if 
people need more time to prepare. I also suggest we adopt GitHub's pull 
request workflow together with the bots from project Skara.

Adopting pull requests and the Skara bots means that the review process 
would work partly through GitHub. In particular, all changes must start 
out as pull requests. Skara automatically generates webrevs, "RFR" 
emails and supports bi-directional syncing between mailing lists and 
GitHub for those that prefer using webrev and the mailing lists. If you 
are unfamiliar with GitHub and pull requests, I suggest checking out 
GitHub's guide [5]. Note that project Skara also provides CLI tools for 
interacting with GitHub for those that prefer working from a terminal. 
You can find more info about these tools on the Skara wiki page [6] or 
from the Skara README [7].

One question I would like to discuss is whether we should split the 
current repository into two; one repository for the ffi work and one 
repository for the vector API work (named e.g. panama-ffi and 
panama-vector). Having these two distinct features in separate 
repositories might make it easier for newcomers and followers to 
understand where the latest changes are. We would still share the same 
mailing list, but having two repositories would separate the streams of 
traffic on GitHub, i.e. each project would have it's own, separate, set 
of pull requests.

If you have any comments or questions regarding this transition, please 
reply to this thread.


[1] :
[2] :
[3] :
[4] :
[5] :
[6] :
[7] :

More information about the panama-dev mailing list