Skip to main content
Jump to: navigation, search

Build Workshop 1

Revision as of 18:49, 15 August 2006 by (Talk | contribs) (How to register)

Release engineering is important and we're going to pay more attention to it. This workshop is our first step.

As experienced software developers, we all know that release engineering is an essential part of building high-quality frameworks and tools. The Callisto Simultaneous Release demonstrated that truth yet again. Motivated by our desire to reduce the manual overhead of cross-project release engineering for the upcoming Europa Release, the Planning Council endorsed this symposium/workshop for sharing tools and best practices for build/release engineering.


The session will meet from 8 am to 5 pm each of two days. We recommend you arrive the evening before the first day and stay through at least 4 pm the second day. We will provide breakfast and lunch each day. There will be a no-host dinner the evening of the first day.

  • August 12, 2006 -- Early registration ends
  • September 11, 2006 -- Recommended evening arrival
  • September 12 & 13 -- Working Sessions


The event will be held near Portland, Oregon, in the Barley Room of the historic Edgefield resort hotel. The Edgefield property offers a casual environment with many whimsically decorated spaces for work and play.


  • Collective understanding of each project's current build/release process.
  • Define common interactions/locations/protocols (rss, download directories, update sites, mailing lists, conference calls, etc) with the expectation that these will be required of most Europa projects. For example, perhaps Europa projects will publish their build results via an RSS feed for other projects to consume.
  • Design common build infrastructure (processes, conventions, checklists, builders, tests, web pages, maven?, ant?, buckminster?, pack200, cruise control?, etc) which will be recommended to new Eclipse projects and potentially, optionally, adopted by existing projects which do not already have a sophisticated release engineering process.
  • Formulate requirements/requests to the Eclipse Foundation for build support facilities to be made available for smaller projects.

Who should attend

You should attend if you have had, or will have, build and/or release engineering responsibilities for an Eclipse project. It is important for attendees to have real-world knowledge of their build system - this is not a meeting for managers, it's a workshop for do-ers.

You are also welcome to attend if you have substantial related experience and a willingness to contribute to the symposium's goals.

How to register

Thanks to the Eclipse community's response, the workshop is currently full. But we have a waiting list, so if you aren't currently registered, please get on the waiting list by sending mail to Anne Jacko of the Eclipse Foundation.

These are people who hope to attend, or have already registered to attend.

  • Ward Cunningham, organizer, registered
  • Bjorn Freeman-Benson, Dash release engineer & organizer, registered
  • Scott Lewis, registered. ECF project lead. We've got a simple-but-useful build environment for smaller projects.
  • Pete Mackie, registered. ECF project. Author of the stand-alone workstation Eclipse project build. Hey, its really simple to deploy once you understand just a few details about the environment.
  • Jao Tham, registered. EPF project release engineer.
  • Hubert Leung, registered. TPTP project release engineer.
  • Bill Kayser, registered. Share an office with Ward and Bjorn--hoping to get some ideas for improving our build process, especially conventions for naming and packaging of client libraries based on Eclipse plug-ins.
  • Nick Boldt, registered. Eclipse Modeling project release engineer, incl. EMF, UML2, EMFT, and soon GEF, GMF, etc. Committer for (RSS- & Bugzilla-related tools)
  • Sue Lee, registered. BIRT project build & release engineer
  • Max Feldman, registered. GMF project build/release engineer
  • Denis Roy and Matt Ward, hoping. Eclipse Webmasters
  • Natalie Burdick, registered. Works with Maven; hoping to get some ideas about improving builds in general, and learning how Maven technology might be aligned with Eclipse projects
  • John Casey, registered. Works with Maven; hoping to get some ideas about improving builds in general, and learning how Maven technology might be aligned with Eclipse projects
  • Dennis O'Flynn, registered. Corona project lead. Hoping to improve our build process, escpecially in the area of automated regression testing.
  • Dave Wolfe, registration pending, Aperi (pending Eclipse project) release lead. Our build process is in transition...
  • Pawel Piech, registered. [Device Debugging] project engineer. Only starting with build in the project as we only recently checked in our first plugins.
  • Ted Williams, registration pending
  • Thomas Hallgren, registered, Buckminster project
  • Andrew Overholt and Ben Konrath, Fedora Eclipse and Eclipse Linux Distros Dev - We would like to provide details of the problems we encounter with current build procedures and suggest improvements to these procedures to make packaging the SDK and feature sets for Linux distrobution easier.
  • Kim Moir, registered, Eclipse Project release engineer

How to get there

Edgefield is 20 minutes from downtown Portland, Oregon, five minutes from the Columbia River Gorge National Scenic Area, and 15 minutes from Portland International Airport.

There is an Airporter that would run $25, $3 for each additional passenger.

We will use this space to coordinate ride sharing from the airport to the workshop.

  • Ward Cunningham, I will be driving from my home in Portland. I could swing by the airport but my small car has only room for one more.

Things to be discussed

We will use this space to discuss tools, methods, protocols and conventions that should be of interest to the participants.

I think we need to come up with a list of the common challenges that people face with their build infrastructure. Also, it would be good to have a list of issues that arose during Callisto that we'd like to have addressed. Also, what are their best practices can teams share with others? It might be useful to ask people to prepare material in advance on topics they'd like to share. For instance, if you use RSS feeds today, how did you implement it? How could other teams leverage your work? How did you use new pde build functionality in your build? How can others implement this? For each issue that we agree needs to be addressed, we need to have a dynamic team of individuals willing to own the problem and solve it. Otherwise, we will just talk and the problems will remain.

For the goal of "Collective understanding of each project's current build/release process" it would be useful for each attendee to prepare a five minute "lightening talk" that provides an overview of their build process including the advantages and disadvantages of this approach. This will give everyone a background on the various build processes without consuming too much time.

-- Kim Moir


The workshop will alternate between plenary and breakout sessions. Attendees will collectivly select breakout topics in plenary session, tangibly contribute in self-assigned breakouts, and then reconvene to summarize results for the whole.

Breakout groups will be expected to quickly identify issues, review likely solutions, and recommend action appropriate to the Europa timeframe. Each group will draft written conclusions in this wiki that will be the basis of their report in the following plenary.

Tuesday, Sept 12

  • (30 min) Introduction to the workshop, its roots in Callisto, and a vision for its most valuable contribution to Europa. -- Ward Cunningham and Bjorn Freeman-Benson
  • (90 min) Lightning retrospectives presenting current systems, best practices, pain points and wish lists. We recommend these be presented from notes prepared in this wiki and following our Lightning Retrospective Guide as appropriate. -- All Attendees
  • (15 min) Snack and email break
  • (90 min) Lighting retrospectives continued.
  • (60 min) Lunch and email break
  • (30 min) Topic brainstorm and first cut prioritization. We will use some variation of "cast each of five votes on most important topics". Although topics will probably not be surprising, attendees will begin choosing how to apply their efforts the remainder of the day.
  • (60 min) First breakout meeting
  • (15 min) Snack, email and wiki writing break
  • (30 min) First summary reports and discussion
  • (60 min) Second breakout meeting
  • (15 min) Snack, email and wiki writing break
  • (30 min) Second summary reports and discussion

At this point we will break before assembling for dinner. We expect attendees to enjoy Edgefield recreations before and after dinner. However, we hope that the issues of the day and the opportunities for tomorrow will be frequent topics of conversation.

Wednesday, Sept 13

  • (30 min) Reconvene, overnight reflection. We may have an invited speaker in which case we will enlarge this spot. -- Ward Cunningham
  • (60 min) Third breakout meeting
  • (15 min) Snack, email and wiki writing break
  • (30 min) Third summary reports and discussion
  • (60 min) Fourth breakout meeting
  • (15 min) Snack, email and wiki writing break
  • (30 min) Fourth summary reports and discussion
  • (60 min) Lunch and email break
  • (60 min) Fifth breakout meeting
  • (15 min) Snack, email and wiki writing break
  • (30 min) Fifth summary reports and discussion
  • (90 min) Consolidation, assessment and call to action -- Bjorn Freeman-Benson, et. al.

At this point the formal workshop will be over. We expect eastbound attendees to stay over for early morning flights. Again Edgefield has many recreations but some may choose to tour Portland or the Columbia Gorge. We recommend attendees self-organize so as to enjoy each other's company.

Back to the top