Our plan for running the OpenJDK 6 project would essentially be to continue the excellent work done by Andrew Haley. More specifically, we would ensure that we respond promptly to any questions posted on the jdk6-dev mailing list (the amount of traffic on this list is very low, so we don't see this as requiring a lot of resources). Since Azul is a Java source code licensee of Oracle's and still supports customers using JDK 6 our intention is to continue to backport fixes where applicable and integrate them back into the OpenJDK 6 source tree in a timely manner. We will also confirm that any fixes integrated into OpenJDK 6 are in conformance with the relevant specifications using the JCK. We feel this will continue to provide benefit to the wider OpenJDK user community.
Thanks, Andrew > On Dec 7, 2016, at 12:51 PM, Andrew Haley <a...@redhat.com> wrote: > > On 06/12/16 20:29, Andrew Brygin wrote: > >> Azul Systems would still like to offer to take over leadership of this >> project from the beginning of next year. To comply with the Bylaws of >> the OpenJDK 6 project, the Project Lead needs to have Committer status >> on the project. Simon Ritter does not have this status and so he is not >> eligble (at this time) to lead the project. Since I am a committer on >> the OpenJDK 6 project I would therefore like to offer to represent Azul >> as Project Lead. > > When a Project is created, or when its Project Lead resigns or > departs, candidates for a new Project Lead may be nominated by the > Group Leads of a Project’s Sponsoring Groups. Such a nomination > must be approved by a Three-Vote Consensus of these Group Leads. > > The sponsoring group is the Build Group, and the lead is Tim Bell. I > have no objection to your taking this role. However, I think we need > to have a conversation, preferably in public, about how you intend to > run this project. It's not good to do this in the dark. > > Andrew.
