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

Check if any changes in branch master need to be merged into java-10-gradle #374

Closed
cyrille-artho opened this issue Jul 19, 2023 · 7 comments

Comments

@cyrille-artho
Copy link
Member

Before we make the Java 11 version official, let's ensure we are not missing out on any important changes/fixes from master.

@cyrille-artho
Copy link
Member Author

We can use the branch comparison feature in GitHub to see if some of the 1300+ deletions are things we want to keep: master...java-10-gradle
Most deletions are parts of changes (- for master branch, + for java-10-gradle branch), but perhaps a few were fixes that were only applied to master. These could also be documentation or typos in comments.
We would like that several of us review this branch comparison to ensure we don't miss anything.

@varad64
Copy link
Contributor

varad64 commented Jul 29, 2023

Hello @cyrille-artho, upon thoroughly reviewing all the changes via GitHub's comparison feature, I have found that the 1,327 deletions are direct replacements, changes to ensure better compatibility and refactoring. None of the deletions made show up in the branch comparison feature.

However, when these files are compared by looking within their respective branches, there are fixes that were applied to only the master branch. The files which have had fixes only on the master branch are as follows:

Out of the 217 changed files reviewed, the above 13 files have fixes that need to be incorporated into the java-10-gradle branch.

Some files do exist such that, they have changed on the master branch but are not included by the branch comparison tool as the same file has not been modified on the java-10-gradle branch. For example, jpf/vm/Types.java file which has been updated with a fix for #204.

I am reviewing all files to make sure we do not miss such fixes.

Thanks!

cc @pparizek

@varad64
Copy link
Contributor

varad64 commented Aug 4, 2023

Hello @cyrille-artho and @pparizek, following up on my last comment about identifying files modified only on the master branch, so as to not skip any fixes/features before making the java-10-gradle the default branch. All such files have been identified after thorough investigation and there are 43 such files, please find them categorised as below:

Thank you!

@varad64
Copy link
Contributor

varad64 commented Aug 17, 2023

Hello @cyrille-artho and @pparizek, a total of 35 pull requests / commits were identified which modify the above listed files only on the master branch. The changes comprise bug fixes, addition of functionality and documentation updates.

After going through all the 35 patches, please find the updates as below:

  1. 27 patches successfully pass. Updates were necessary for some patches to work as expected.
  2. 3 patches related to Types, ClassLoaderTest are on hold as Modify Types.instanceOf to take a ClassInfo as LHS #410 which modifies the same set of files and tests modified by the patches
  3. 4 patches related to the String class and its native peer as the implementation of the String class has changed, and these patches are no longer relevant and 1 patch which adds a JPF example has been skipped as it does not meet the standards prescribed and lacks proper documentation.

All of the details about the patches applied has been maintained here.

Thanks!

@varad64
Copy link
Contributor

varad64 commented Aug 23, 2023

Hello @cyrille-artho and @pparizek, the exercise of applying patches that either add new functionality or fix bugs, from the master branch to the java-10-gradle branch is now complete.

The patches that were on hold due to #388 and 388 itself have now been included in the list and a related patch, #208 is also added. This takes the total tally of patches to 37, and of these:

  1. 32 patches have been applied and successfully pass.
  2. 4 patches, related to the String class and its native peer have been skipped as the implementation of the class has been changed.
  3. 1 patch has been skipped as Modify Types.instanceOf to take a ClassInfo as LHS #388 redefines and adds to the former.

All details about can be found in this spreadsheet.

Thanks!

@cyrille-artho
Copy link
Member Author

Great, so we can close this issue now, right?

@varad64
Copy link
Contributor

varad64 commented Aug 24, 2023

Yes @cyrille-artho, good to close this issue now.
Thanks!

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

No branches or pull requests

2 participants