From mark.reinhold at oracle.com  Thu Oct  6 21:04:28 2011
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Thu, 06 Oct 2011 21:04:28 -0700
Subject: openjdk.java.net offline this weekend
Message-ID: <20111007040428.890AAF7E@eggemoggin.niobe.net>

In order to upgrade datacenter facilities, the servers that host
openjdk.java.net and its subdomains will be offline from 4:00 UTC
on Saturday, 7 October until 20:00 UTC Monday, 10 October.

(For those in US/Pacific, that's 8pm Friday to noon Monday.)

- Mark

From mark.reinhold at oracle.com  Tue Oct 25 09:43:33 2011
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Tue, 25 Oct 2011 09:43:33 -0700
Subject: OpenJDK Community Bylaws: Installed
Message-ID: <20111025164333.F0D2E943@eggemoggin.niobe.net>

Now that the Census [1] has been completed and cross-checked, and
some necessary documentation prepared, the OpenJDK Community Bylaws
are now officially in effect.

The Bylaws and the Census have new, permanent homes:

    http://openjdk.java.net/bylaws
    http://openjdk.java.net/census

The Census will be updated on demand as people, Groups, and Projects
come and go.

The Group and Project overview pages have been rewritten:

    http://openjdk.java.net/groups/
    http://openjdk.java.net/projects/

These pages now give both advice and step-by-step instructions for
nominating Contributors to new roles and for proposing new Groups
and Projects.  (Thanks to Iris Clark for these updates.)

Finally, the OpenJDK Members Group has been created:

    http://openjdk.java.net/groups/members/

If you are an OpenJDK Member then you will automatically be added to
that Group's mailing list.

- Mark


[1] http://mail.openjdk.java.net/pipermail/announce/2011-August/000108.html

From mark.reinhold at oracle.com  Mon Oct 31 10:35:08 2011
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Mon, 31 Oct 2011 10:35:08 -0700
Subject: OpenJDK bug database: JIRA pilot deployment
Message-ID: <20111031173508.365E9DD3@eggemoggin.niobe.net>

We (i.e., Oracle) have decided to move ahead with a pilot deployment of
JIRA for use by the OpenJDK Community.

In our view JIRA offers several important advantages over the principal
competition, namely Bugzilla [1][2]:

  - Easier customization -- JIRA has a well-documented and supported
    plugin API, whereas extensions to Bugzilla seem (most often) to
    require changes to its core code.

  - Less integration work -- JIRA already integrates well with a review
    system (Crucible) and a code-browsing system (FishEye), as well as
    some related systems, right out of the box.  With Bugzilla we'd have
    to integrate such disparate systems ourselves.

  - Multiple customizable workflows -- We have a clear need to support
    multiple workflows, not just for bugs but also for API change reviews
    (to replace the current internal "CCC" process) and for tracking the
    status of ongoing feature work.  JIRA supports multiple workflows,
    but Bugzilla does not.

It's true that JIRA is not an open-source product, and I understand why
some people are uncomfortable with that.  What's important, however, is
that the data in this JIRA instance will be openly available as required
by the Bylaws [3].

We hope to deploy a JIRA pilot instance in the next few months for use
by non-JDK Projects within OpenJDK.  If that goes well then we'd look
to migrate the current JDK bug corpus from Oracle's legacy internal
system to JIRA by mid-2012.

- Mark


[1] http://mail.openjdk.java.net/pipermail/web-discuss/2011-May/000221.html
[2] http://cr.openjdk.java.net/~mo/openjdk/bugsystem/BugzillaJIRAComparison.pdf
[3] http://openjdk.java.net/bylaws#_A