Coherent release process

David Holmes david.holmes at oracle.com
Fri Nov 20 03:51:51 UTC 2015


Trivial patches can be accepted without the provider being an OCA 
signatory. However the patch must be provided using OpenJDK technology 
so it can't be taken from an external website, but if small enough 
should be included inline in an email message.

Thanks,
David

On 20/11/2015 1:45 PM, Quanah Gibson-Mount wrote:
>
> --On Thursday, November 19, 2015 10:34 PM -0500 Andrew Hughes
> <gnu.andrew at redhat.com> wrote:
>
>> [Adding in the 8u mailing list]
>>
>> ----- Original Message -----
>>> Hi,
>
> Hi Andrew,
>
> Thanks for the follow up!
>
>
>> Actually, that won't get you u66 unless you explicitly check out a tag.
>> The current tip of 8u is currently receiving fixes people are pushing for
>> u76, which I believe is due to be released next April, at the same time
>> as the u75 security update, which will be based on u72.
>
> Yes, I use a tag for building.  However, that process is completely
> unreliable UNLESS you use my patch, because the tag is not passed down
> when pulling out the sub modules, which means you get mismatched code.
> I.e., without my patch, you cannot build a consistent OpenJDK release
> against a specific tag.
>
>>> <http://fpaste.org/289480/44729880/>
>>>
>>> As we rely heavily on being able to provide up to date, consistent,
>>> secure OpenJDK builds to our customers, having the process to build new
>>> releases be reliable is of significant importance.  I imagine that is
>>> the case for many others as well.
>>
>> Another problem I've also observed. I'm happy for you to ping me if you
>> have a patch and need a bug opening (I've done this for colleagues at Red
>> Hat), but as Dalibor mentions in response, the OCA needs to be sorted
>> first. There's not much point opening a bug with a patch if the patch
>> can't be committed for legal reasons.
>
> I can't see why it'd be a problem to have the patch committed.  It's
> literally modifying hgforest.sh to include the ${command_args} command
> line options that were originally passed get_source.sh.  Again, without
> this patch, there is literally no way to build OpenJDK where all
> portions of the checkout from mercurial are fixed to a given tag.
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Platform Architect
> Zimbra, Inc.
> --------------------
> Zimbra ::  the leader in open source messaging and collaboration


More information about the jdk8u-dev mailing list