Crypto has been added to OpenJDK

[Brad Wetmore]

> From our experience on planet.classpath.org, the 'other' side of the
> people one's working together in a free software project is pretty
> important in creating the sort of social glue that binds communities, in
> particular in virtual ones. ;)

Good point, I was afraid of appearing vain by posting personal stuff on 
a work blog.

>> Anyway, this quality perspective is "common knowledge" to us
>> gatekeepers, so it might be worth sharing details about what really goes
>> on in the trenches.  It is probably a good topic for a blog rather than
>> this email, so maybe I'll get off my duff and do it soon.
> 
> Yes, please. ;)

Ok, fair enough, I'll be out of the office for a bit, and will try to 
get something when I return.

> Speaking of that ... what sort of an automated build system do you use,

Release Engineering, the folks who do the official builds, and our 
quality folks are much better funded that we integrators.  ;)

I and probably most integrators use systems and homebrew scripts 
accumulated over the years.  Each night or just before an integration, I 
take everything submitted to my Security/Networking gate, sync it with 
the MASTER gates, then drop everything into a build/test environment I 
developed.  It's a distributed build system, which syncs to a common 
workspace, then forks off a build/test job to each of the major 
platforms.  I tried to mimic our RE environment, so I do full "control" 
builds, minus hotspot/install.

As for testing, we integrators generally run the tests for our 
respective functional area(s), including the regression, JCK, and 
Quality trees.  As our build machines are also our development machines, 
and since JDK is so huge, we just can't test everything.  We just don't 
have the iron for it.

There's been some standardization on integration build/test scripts in 
the past (mainly client), but each gatekeeper generally has completely 
different requirements so there's a number of integration build/test 
systems out there.  For me, I had to keep some source on a completely 
different machine and thus do separate subbuilds.  I looked at a number 
of different gatekeeper environments before I decided I'd have to write 
my own.  The other systems just didn't do what I needed without a lot of 
hacking.

> and do you plan to make the build status for the different
> configurations available, a la mozilla's tinderbox [1]?

Tinderbox looks like a nice setup.  I don't know what RE has available. 
  I know they do nightly builds, but don't know what testing is done. 
That would be something for RE or the quality folks to comment on.

JPRT, an internal build system for developers, holds some promise of a 
common automated build system, but there are still limitations on how 
much it can do.

     http://blogs.sun.com/kto/entry/jprt_sun_hardware_is_so

Oh, did I mention that gatekeeping is only supposed to be part of our 
job.  We're "full time" developers as well.  When people introduce 
breakage, that directly cuts into the time we have to get "real" work 
done, like say...*gasp*...opening the JCE source.  :)  With the amount 
of code reorganization for OpenJDK and the upcoming transition to 
mercurial, it's been a...(wait for it...wait for it)...challenge...  ;)

Gads, that's probably another blog entry I just wrote.  I should go get 
started on that and stop boring you good folks at discuss at openjdk.

Brad