Crypto has been added to OpenJDK

[Dalibor Topic]

Brad Wetmore wrote:
> 
> Dalibor Topic wrote:
>> Janet Koenig wrote:
>>> That's great news!  I know this has been a big challenge so thanks for
>>> continuing to drive this and making it happen!
>>> Regards,
>>> Janet
>>
>> Thanks from over here, too.
> 
> You're welcome.  It was a...challenge, as Janet said.  :)

I bet. Thank you very much for pushing through.

>> No blog on planetjdk.org on it yet? ;)
> 
> I've yet to create a blog.  It's been on my to-do list for far too long.
>  I would probably end up blogging about my outside pursuits, which might
> be boring unless you like marching bands, travel, or pyrotechnics (not
> the internal politics kind, but the ones in the sky).  ;)

>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. ;)

> I should really create one, I've got a couple topics that you might be
> interested in from the internal perspective.  I'm one of several
> gatekeepers, so I started writing a couple ideas down about how our
> internal "gatekeeper" process works, and the overall process of getting
> fixes into OpenJDK while making sure the quality stays up.  The quality
> *HAS* to stay up, as people will be betting their businesses (or have
> already) on the code all of us will be developing.  Coding in this
> project is an awesome responsibility, and one that is sometime lost by
> people who just want to "play with something."

Great, I think it would be fascinating to hear more about the processes
you have in place internally, and how you see them evolve/adapt for
OpenJDK.

For those of us outside Sun, the more transparent the 'black process
boxes' are, the better we can understand what's going on, and where to
assist to get things moving in the right direction, if possible/desirable.

> 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. ;)

> Oh, and how the coming switch to Mercurial will rock our internal world.
>  So many build/test scripts to update.
> 
> Brad
> 
> P.S.  When I had gatekeeper duty years ago, if someone "broke the
> build," I would hang a hangman's noose made from an power cord over
> their office doorway.  You didn't want the noose, because everyone knew
> what it meant without saying anything.  I haven't quite figured out how
> to do a virtual noose, so please, just don't "break the build."  ;)

Speaking of that ... what sort of an automated build system do you use,
and do you plan to make the build status for the different
configurations available, a la mozilla's tinderbox [1]?

cheers,
dalibor topic

[1] http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox