Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Europa Build Workshop - Best practices


I think we are heading at least a little bit in that direction.  For example, EMF's release engineer, Nick Boldt, is a committer on the base builder component to help support things like RSS feeds for builds in a way that's directly reusable by any other team.  We too would like to see a more centralized effort that avoids duplication and that helps share best practices by virtue of incorporating them in a common base builder, so we are taking steps ourselves in that direction.  The only danger here is that some folks may try to off-load their "requirements" onto an over-worked, under-appreciated, set of folks, rather than helping contribute.  But that's probably a very small danger with the great community we have at Eclipse, and besides, we can just ignore folks like that.  ;-)

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 969)

"Ed Burnette" <Ed.Burnette@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

10/03/2006 12:28 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
RE: [cross-project-issues-dev] Europa Build Workshop - Best practices

I know Kim's going to throw something at me, but has it been considered to have one shared (bigger) release engineering team for all Eclipse projects rather than each project doing their own builds? I know this goes against the idea of having projects be independent, but are build reliability, plug-in version numbering schemes, and build terminology really something that different projects need to differentiate themselves with?
I would imagine that Linux distros for example are going to want to learn one way of building 'eclipse' and not 10 different ways to build the different projects with their own little quirks. I would also imagine that if I were starting a new project I'd like to concentrate on coding and not trying to understand all the build rules and numbers and tools.

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim Moir
Tuesday, October 03, 2006 11:50 AM
Cross project issues
[cross-project-issues-dev] Europa Build Workshop - Best practices

At the Europa build workshop (, one of the action items that  arose was the desire to share best practices and tools across projects with respect to release engineering.  We discovered that multiple teams have written tools with similar functionality to incorporate into their builds, such as comparing plugins and feature versions across releases, api comparison tools and others .  It makes sense to share these tools instead of duplicating committer efforts.

We also learned that teams that recompile our builds for redistribution, for example, linux distrubutions, have suggestions on how to make our builds easier to reproduce  for their respective communities.  We heard from new eclipse projects who have had difficulties getting their builds started and hope that these best practices will be able to help them out.   I invite you to add any recommended techniques or tools that you have incorporated into your builds to the list on the wiki.

cross-project-issues-dev mailing list

Back to the top