From mark.reinhold at oracle.com Thu Mar 1 08:00:00 2012 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 01 Mar 2012 08:00:00 -0800 Subject: OpenJDK Governing Board Election: Nominations Please Message-ID: <20120301155810.63950835@eggemoggin.niobe.net> The OpenJDK Governing Board manages the structure and operation of the OpenJDK Community [1]. It has two At-Large Members who serve for a term of one calendar year, starting on the first day of April each year [2]. The two-week nomination period for candidates to fill those seats is now open. It will end at 16:00 UTC on Thursday, 15 March 2012 [3]. During this time any OpenJDK Member [4] may nominate an individual who does not currently hold an appointed Governing Board seat to fill one of the At-Large seats. That individual need not already be an OpenJDK Member. An OpenJDK Member may make more than one such nomination. To nominate someone, send an e-mail message to members at openjdk.java.net with the subject line "GB Nomination: $NAME", where $NAME is the full name of the person you're nominating. Use the body of the message to make the best case you can for your nominee. Nominees must accept their nominations by the start of voting. Those who do accept will be invited to submit short candidate statements to be posted on the election page [5]. Voting will start on Friday, 16 March 2012 and run for two weeks. All OpenJDK Members are eligible to vote. Detailed information on voting logistics will be available shortly. - Mark [1] http://openjdk.java.net/bylaws#_9 [2] http://openjdk.java.net/bylaws#at-large-members [3] http://timeanddate.com/worldclock/fixedtime.html?msg=OpenJDK+GB+Nominations+Close&iso=20120315T16&sort=1 [4] http://openjdk.java.net/census#members [5] http://openjdk.java.net/poll/gb/2012/ From mark.reinhold at oracle.com Thu Mar 15 12:45:43 2012 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 15 Mar 2012 12:45:43 -0700 Subject: OpenJDK bug database: Status update Message-ID: <20120315194543.C1780AB5@eggemoggin.niobe.net> Last October I announced Oracle's intent to deploy a pilot JIRA instance for use by the OpenJDK Community within a few months and then, if all goes well, to migrate the JDK bug corpus from Sun's creaky old legacy internal system to a public JIRA instance by mid-2012 [1]. Following that announcement Iris Clark initiated and moderated the first of a planned series of discussions about the design and configuration of the system [2][3]. In parallel Mohan Pakkurti and his team have been working to implement the pilot system; this includes configuring JIRA, acquiring and provisioning hardware, and getting the myriad internal approvals required from various parts of Oracle. All of this work is, unfortunately, taking much longer than anticipated. We remain committed to the ultimate goal of making a public JIRA instance available, but at this point we don't think we can deliver it in the next few months. In the meantime it's now mid-March, and the legacy internal system is going to be shut down in late July. Faced with these constraints, we must change our plan. Rather than make a public pilot system available first, we're initially going to migrate the JDK bug corpus from the legacy internal system to an internal JIRA instance. Our goal is to complete that transition by mid-June, and in order to do that we've assigned several more Oracle engineers to the effort. We'll move to an external public JIRA instance some time later, once the hardware is in place and the necessary approvals are obtained. In order to speed the migration process the initial JIRA instances, both internal and external, will not be as deeply customized as envisioned in Iris's draft [3]. Some of the ideas in the draft will no doubt influence the design of the initial systems; the remainder will be reconsidered after the public system is available. I understand that this news will be disappointing to many; I'm not very happy about it myself. It's unfortunate that there won't be a public pilot system prior to the migration, that deep customization work will have to wait, and that the public system most likely won't be available by mid-2012. It will be far worse for all concerned, however, if there is not even a working internal bug system for the JDK by the time that Sun's legacy system is shut down. This new plan therefore places the highest priority on migrating off of that system. Oracle remains firmly committed to making a public system available as soon as possible after that. - Mark [1] http://mail.openjdk.java.net/pipermail/announce/2011-October/000112.html [2] http://mail.openjdk.java.net/pipermail/discuss/2011-December/002237.html [3] http://cr.openjdk.java.net/~iris/jira/JIRAforOpenJDK.html From jonathan.gibbons at oracle.com Thu Mar 22 16:46:50 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 22 Mar 2012 16:46:50 -0700 Subject: CFV: New Project: Code Tools Message-ID: <4F6BB9EA.6090904@oracle.com> I hereby propose the creation of the Code Tools Project[1] with Jon Gibbons as the Lead and the Compiler Group as the sponsoring Group(s). The goal of the Code Tools Project will be to provide tools of use to OpenJDK developers while working on the OpenJDK code base. Such tools currently include test tools and Mercurial extensions; it is envisaged that additional tools will be added over time, after discussion on the Project's main mailing list, and subject to the Project Lead's approval. There are a number of initial candidates for inclusion in such a Project. * jtreg jtreg is the regression test harness for the OpenJDK platform. It is currently just available via source bundles [2]. * jtharness jtharness is the test framework underlying jtreg [3]. * sigtest sigtest is a set of utilities relating to API signature checking [4]. * the Mercurial "jcheck" extension jcheck provides simple validity checks on the contents of a changeset Jon has long been involved in the tools aspects of testing JDK. He designed the original JavaTest harness, underlying both JCK and jtreg. Since joining the JDK LangTools team, he has led the way in improving the reliability of test runs, both by improving tests and/or the jtreg test harness. The suggested sets of initial reviewers and committers are based upon the contributors to the initial set of tools listed above. The suggested initial set of Reviewers is: Mark Reinhold John Coomes Iris Clark Brian Kurotsuchi Dmitry Fazunenko Mikhail Ershov Kevin Looney Andrey Titov In addition, the suggested initial set of Committers is: Larry Hoffman Dawn Phillips Votes are due by 7:00AM UTC, Friday 6 April [7]. Only current OpenJDK Members [5] are eligible to vote on this motion. For Lazy Consensus voting instructions, see [6]. -- Jon Gibbons [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html [2] http://openjdk.java.net/jtreg [3] http://jtharness.java.net/ [4] http://sigtest.java.net/ [5] http://openjdk.java.net/census/#members [6] http://openjdk.java.net/projects/#new-project-vote [7] http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224