Jump to: navigation, search

Difference between revisions of "Europa Build Workshop Breakout Results"

 
(Buckminster/Maven)
Line 19: Line 19:
  
 
==Buckminster/Maven==
 
==Buckminster/Maven==
 +
* Common model
 +
** Backbone
 +
** Graphical model input
 +
** Buckminster and Buckminster model
 +
** Maven in Eclipse and Maven model
 +
** Maven
 +
* Suggest that they adopt a Europa project and help revise that project's build. Nick volunteered one of the smaller EMFT projects; another candidate is BIRT (Sue); don't want to take on too much - want one/few good success stories rather than broad swath of mediocrity
 +
* Document the process as a part of working with one of the projects.

Revision as of 18:22, 12 September 2006

Build Best Practices Breakout

(computer crashed in the middle of typing in the result)

  1. Proper version numbering
  2. Making builds reproducible
  3. Tag files from each release with the same human-readable tag
  4. API checking tool from WTP
  5. avoid circular dependencies
  6. documentation up-to-date; current link available on website; remove old content
  7. backup redundant systems
  8. separate publishing script from “build” (compilation)
  9. able to turn functions on the build on or off e.g. turn off publishing
  10. regularly scheduled builds
    1. public humiliation
    2. send email to mailing list
    3. send email to plug-in owner
  11. have an update site; optimize update sites
  12. pack 200
  13. feature design – group plug-ins based on functional grouping

Buckminster/Maven

  • Common model
    • Backbone
    • Graphical model input
    • Buckminster and Buckminster model
    • Maven in Eclipse and Maven model
    • Maven
  • Suggest that they adopt a Europa project and help revise that project's build. Nick volunteered one of the smaller EMFT projects; another candidate is BIRT (Sue); don't want to take on too much - want one/few good success stories rather than broad swath of mediocrity
  • Document the process as a part of working with one of the projects.