Proposal to revise forest graph and integration practices for JDK 9

[Paul Sandoz]

On Dec 2, 2013, at 8:35 PM, Jonathan Gibbons <jonathan.gibbons at oracle.com> wrote:

> On 12/01/2013 09:14 PM, Joe Darcy wrote:
>> We've found the "Continuous Delivery" book by Jez Humble and David Farley to be useful.
>> 
>> Some relevant quotes from the first chapter or two of that text:
>> 
>>> 
>>> If It Hurts, Do It More Frequently, and Bring the Pain Forward
>>> "This is the most general principle on our list, and could perhaps best be described as a heuristic. But it is perhaps the most useful heuristic we know of in the context of delivering software, and it informs everything we say."
>>> 
>>> Integration is often a very painful process.
>>> "If this is true of your project, integrate every time somebody checks in, and do it from the start of the project.
>>> If testing is a painful process that occurs just before release, don’t do it at the end. Instead, do it continually from the beginning of the project." 
> 
> I like the term "Continuous Delivery" as compared to "Continuous Integration" since Integration is such as loaded term in our current infrastructure.
> 
> I also like +100 the comment about testing ...
> 

Also... continuous delivery of openjdk builds, preferably labeled with the changeset id corresponding to the tip of the build.

That will make it much easier for developers to verify a fix. I don't like saying "I have fixed the issue in tl, but you will have to wait a week or so until build XXX appears" (so "old skool") thus making it harder to spin faster and get feedback.

Paul.