From jai.forums2013 at gmail.com Mon Jun 2 09:30:44 2025 From: jai.forums2013 at gmail.com (Jaikiran Pai) Date: Mon, 2 Jun 2025 15:00:44 +0530 Subject: =?UTF-8?Q?Result=3A_New_JDK_Committer=3A_Volkan_Yaz=C4=B1c=C4=B1?= Message-ID: Voting for Volkan Yaz?c? [1] is now closed. Yes: 17 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the nomination. [1] https://mail.openjdk.org/pipermail/jdk-dev/2025-May/010083.html -Jaikiran From magnus.ihse.bursie at oracle.com Wed Jun 4 07:03:56 2025 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Wed, 4 Jun 2025 09:03:56 +0200 Subject: Anyone still using CommentChecker and DirDiff? Message-ID: Hi, There are two tools in src/utils/src/build/tools, CommentChecker.java and DirDiff.java. As far as I am aware, these are abandoned and could be removed. I propose to do this in JDK-8358543. If anyone is still using any of these tools, now is the time to say so. /Magnus From mark.reinhold at oracle.com Wed Jun 4 17:37:19 2025 From: mark.reinhold at oracle.com (Mark Reinhold) Date: Wed, 4 Jun 2025 17:37:19 +0000 Subject: JEP proposed to target JDK 25: 509: JFR CPU-Time Profiling (Experimental) In-Reply-To: <20250528162247.7CB628174E4@eggemoggin.niobe.net> References: <20250528162247.7CB628174E4@eggemoggin.niobe.net> Message-ID: <20250604133717.999000045@eggemoggin.niobe.net> 2025/5/28 12:22:48 -0400, mark.reinhold at oracle.com: > The following JEP is proposed to target JDK 25: > > 509: JFR CPU-Time Profiling (Experimental) > https://openjdk.org/jeps/509 > > Summary: Enhance the JDK Flight Recorder (JFR) to capture CPU-time > profiling information on Linux. This is an experimental feature. > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > is more than welcome, as are reasoned objections. If no such objections > are raised by 17:00 UTC on Wednesday, 4 June, or if they?re raised and > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > I?ll target this JEP to JDK 25. Hearing no objections, I?ve targeted this JEP to JDK 25. - Mark From alexey.ivanov at oracle.com Wed Jun 4 18:03:19 2025 From: alexey.ivanov at oracle.com (Alexey Ivanov) Date: Wed, 4 Jun 2025 19:03:19 +0100 Subject: CFV: New JDK Committer: Daniel Gredler (dgredler) In-Reply-To: References: Message-ID: Vote: yes On 26/05/2025 21:38, Philip Race wrote: > I hereby nominate: Daniel Gredler (dgredler) [1] to JDK Committer. -- Alexey From 333alaamo at gmail.com Wed Jun 4 20:46:42 2025 From: 333alaamo at gmail.com (Alaa Mohamed) Date: Wed, 4 Jun 2025 23:46:42 +0300 Subject: "Scoped Mutable Variables" In-Reply-To: References: Message-ID: Thank you for your feedback. On Thu, 22 May 2025, 6:57 pm Chen Liang, wrote: > Hello, I don't think this proposal "reduce unintended side effects caused > by variable mutations in nested blocks". This massively decreases the > readability of code. Your purposed problem can be solved by declaring new > non-final local variables in the nested scopes and making the main local > variable final, and there is no proof that your proposed problem actually > happens in development. You can search for Static Single-Assignment form > for more efficient usages of variables that is both more human and machine > friendly. Also on a side note, Java Language feature discussions usually > happen on compiler-dev list. > > Regards, Chen Liang > ------------------------------ > *From:* jdk-dev on behalf of Alaa Mohamed < > 333alaamo at gmail.com> > *Sent:* Wednesday, May 21, 2025 8:54 PM > *To:* jdk-dev at openjdk.java.net > *Subject:* "Scoped Mutable Variables" > > > Dear OpenJDK Reviewers and Community, > > I hope this message finds you well. > > Please find attached my draft Java Enhancement Proposal (JEP) titled > "Scoped Mutable Variables" (JEP XXXX), which introduces a new variable > declaration modifier scoped. This modifier allows variables to be mutable > exclusively within a limited lexical scope (such as inside if, for, or > while blocks) without affecting the variable?s value in the enclosing or > global scope. > > This proposal aims to reduce unintended side effects caused by variable > mutations in nested blocks, thereby improving code safety and readability > in large-scale Java projects. > > I would appreciate any feedback or suggestions you may have on the design, > naming, integration approach, or any other aspect of the proposal. > > Please find the full proposal text attached (or below). > > Thank you very much for your time and consideration. > > Best regards, > Alaa Mohamed > [Your email] > [ GitHub - alaa-333/scoped-variable-jep > ] > > [ LinkedIn : > https://www.linkedin.com/in/alaa-mohamed-1468a3304?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_contact_details%3BOH8SwytOQoO2HCH0VxvdBA%3D%3D > ] > Also for more details : Java Enhancement Proposal (JEP) (1).pdf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias.hartmann at oracle.com Thu Jun 5 14:30:32 2025 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Thu, 5 Jun 2025 16:30:32 +0200 Subject: =?UTF-8?Q?Result=3A_New_JDK_Committer=3A_Manuel_H=C3=A4ssig?= Message-ID: <5ac2d992-18a3-48b1-982a-c3afb9d464f6@oracle.com> Voting [1] for Manuel H?ssig [2] is now closed. Yes: 19 Veto: 0 Abstain: 0 According to the bylaw's definition of Lazy Consensus [3], this is sufficient to approve the nomination. Thanks, Tobias [1] https://mail.openjdk.org/pipermail/jdk-dev/2025-May/010136.html [2] https://openjdk.org/census#mhaessig [3] https://openjdk.org/bylaws#lazy-consensus From mark.reinhold at oracle.com Thu Jun 5 17:20:51 2025 From: mark.reinhold at oracle.com (Mark Reinhold) Date: Thu, 5 Jun 2025 17:20:51 +0000 Subject: JDK 25 is now in Rampdown Phase One Message-ID: <20250605172049.C8E94818632@eggemoggin.niobe.net> Per the JDK 25 schedule [1], we are now in Rampdown Phase One. The overall feature set [2] is frozen. No further JEPs will be targeted to this release. We?ve branched the main line of development, in the master branch, to create the jdk25 stabilization branch: https://github.com/openjdk/jdk/tree/jdk25 Any changes pushed to the master branch are now bound for JDK 26, as noted previously [3]. Since the repository contains multiple active branches, Reviewers and Committers should carefully verify the target branch of every pull request. The stabilization branch is open for select bug fixes and, with approval, late enhancements per JEP 3, the JDK Release Process [4]. If you?re responsible for any of the bugs on the RDP 1 candidate-bug list [5] then please see JEP 3 for guidance on how to handle them. We will integrate most stabilization changes via backports, as we have since JDK 22 [6]: - Most fixes and enhancements intended for the stabilization branch will also be applicable to the main line, in the master branch. Integrate such a change into the master branch first. Then, after you obtain any required approvals, backport it to the stabilization branch using the Skara `/backport` command [7] or, if necessary, by manually opening a backport PR with the title `Backport $HASH`, where `$HASH` is the original commit hash. (The Developers? Guide has guidance on working with branches [8] and backports [9].) - Some fixes will be specific to the stabilization branch and not applicable to the main line. Integrate such fixes directly into the stabilization branch. In order to make sure that no backports are missed, prior to the RDP 2 and RC phases we will remind JDK Contributors to review changes that have been integrated into the main line but not backported to the stabilization branch. These JBS queries can be useful: - Changes not backported from the main line https://bugs.openjdk.org/issues/?filter=44264 - My changes not backported from the main line https://bugs.openjdk.org/issues/?filter=44268 - Mark [1] https://openjdk.org/projects/jdk/25/#Schedule [2] https://openjdk.org/projects/jdk/25/#Features [3] https://mail.openjdk.org/pipermail/jdk-dev/2025-May/010184.html [4] https://openjdk.org/jeps/3 [5] https://openjdk.org/s/jdk-rdp-1 [6] https://openjdk.org/jeps/3#Integrating-fixes-and-enhancements [7] https://wiki.openjdk.org/display/SKARA/Backports [8] https://openjdk.org/guide/#working-with-git-branches [9] https://openjdk.org/guide/#working-with-backports-in-jbs From christian.s.stein at oracle.com Thu Jun 5 17:44:05 2025 From: christian.s.stein at oracle.com (Christian Stein) Date: Thu, 5 Jun 2025 17:44:05 +0000 Subject: jtreg 7.5.2 is here In-Reply-To: References: Message-ID: The integration of jtreg 7.5.2 in JDK 26-ea was done via https://github.com/openjdk/jdk/commit/fe3be498b83e70a9f4739ddad6642c3aa04a97d3 Happy testing! ________________________________________ From: Christian Stein Sent: Monday, May 19, 2025 18:38 To: jdk-dev at openjdk.org Subject: Coming soon: jtreg 7.5.2 JDK folk, This is a general heads-up that jtreg 7.5.2 is ready for use and that we should soon update JDK to use it. The most significant changes in jtreg 7.5.2 are minor improvements. It also contains a few new features and some bug fixes. Find a listing of all noteworthy changes at [1]. The plan is to make jtreg 7.5.2 the default version for JDK 25-ea by end of May 2025. Thanks to everyone who has helped thus far! [1] https://github.com/openjdk/jtreg/blob/jtreg-7.5.2+1/CHANGELOG.md