Over a million developers have joined DZone.

Eclipse Development Process 2014

DZone's Guide to

Eclipse Development Process 2014

· DevOps Zone ·
Free Resource

Learn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.

One of my tasks for this quarter is to deliver a draft of an update to the Eclipse Development Process (EDP) to the Eclipse Architecture Council for their review.

The process that we follow is to open bugs against Community/Architecture Council (prefixed with [EDP]), discuss them, and then incorporate the discussion into the new version of the EDP.

There are currently 19 open bugs, including Bug 367236 which is the “master” bug for this particular iteration. As you can tell from the title, “Updates to the EDP for 2014″, I expect that the Architecture Council-reviewed document will be presented to the Eclipse Board of Directors for their approval for implementation in early 2014. All of the EDP bugs that we intend to address with this iteration have been set as blockers on the “master” bug.

With this iteration, the focus in on simplifying the process and the document. One thing that I expect to include is a reduction in the number of types of reviews (Bug 325004), and considerations for social coding at Eclipse (Bug 415636). There are a few housekeeping items.

While I think it’s an interesting idea, I don’t think that we’ll get to Mickael’s suggestion on Twitter:

There has been enough discussion on these bugs to start drafting the changes. Stay tuned. And, of course, feel free to open additional bugs reports for additional changes.

Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}