valhalla openjdk repository
forax at univ-mlv.fr
Tue May 16 20:14:32 UTC 2017
Hi Karen, hi all,
the main issue i see with branches is that, they easily becomes incompatibles, which means that less people will test before things are integrated in main workspace.
by example for amber, lvti and lambda-leftover both change the frontend compiler in an incompatible way,
even if it can be easily fixed, it's an unnecessary barrier for testing in my opinion.
I believe that the default repo should contains the code of all branches automatically integrated so people will be able to test without messing with branches.
----- Mail original -----
> De: "Karen Kinnear" <karen.kinnear at oracle.com>
> À: valhalla-dev at openjdk.java.net
> Envoyé: Mardi 16 Mai 2017 00:05:04
> Objet: valhalla openjdk repository
> Please hold off making changes to the valhalla openjdk repository until further
> We are in the process of updating the parent to be based off of jdk10/hs to have
> latest changes.
> When the repository is ready, I will let you know.
> We are moving to a branch model, so that we will NOT be pushing changes to the
> valhalla/valhalla repository.
> Instead we will create branches underneath that for specific projects, including
> to start with
> mvt (minimal value types) and
> nest mates (JEP 181: nested class access controls)
> Once those are created, give us time to push the merged code to mvt and then I
> notify you that the repository is open for business.
> p.s. Note that we have saved the existing valhalla repository to
> valhalla/valhalla9 and made it read-only
More information about the valhalla-dev