OpenJDK Members Group Rules in Bylaws

Hi, I just stumbled upon the following phrase in section 8 (OpenJDK Members) of the OpenJDK Bylaws: "Every OpenJDK Membership is subject to automatic Expiration after one year, but will be renewed upon request. A request for renewal must be received within one year of expiration..." I was a

Re: JDK submit repo

On Fri, Mar 9, 2018 at 4:57 PM, wrote: > 2018/3/8 9:57:44 -0800, volker.simo...@gmail.com: >> On Tue, Mar 6, 2018 at 7:05 PM, vladimir.koz...@oracle.com wrote: >>> My understanding is currently it is not enough for *HotSpot* changes. You >>> still need to ask for

Re: JDK submit repo

On Tue, Mar 6, 2018 at 7:05 PM, Vladimir Kozlov wrote: > My understanding is currently it is not enough for *HotSpot* changes. You > still need to ask for sponsor to run additional Hotspot tests. > At FOSDEM 2018, the OpenJDK Lead Mark Reinhold answered my comment

Re: What does submit mean?

So here the Author enters the scene, who has been granted the right to create changesets intended to be pushed into a specific Project’s code repositories. Still not sure why we need him, as the contributor already describes this role more generically as you just explained. On Thu, Jun 16, 2011

Re: OpenJDK Community Bylaws: Second Public Draft

On Wed, Jun 15, 2011 at 11:16 AM, Dalibor Topic dalibor.to...@oracle.com wrote: On 6/15/11 10:42 AM, Volker Simonis wrote: So for me the Author role is a little artificial, because already Contributors have the right to submit changes. Why do you need special rights to create changesets