Difference between revisions of "Build Environment Effort"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Activities already ongoing or finished)
m (Activities already ongoing or finished: eliminate redirect to Building Guide)
Line 27: Line 27:
* Deprecate 4nt in favor of cygwin
* Deprecate 4nt in favor of cygwin
* Switch to a DSCM - speedup and ease SCM part of CWS handling
* Switch to a DSCM - speedup and ease SCM part of CWS handling
* [http://thread.gmane.org/gmane.comp.openoffice.devel.documentation/3231/focus=26592 Rework build documentation] (see results at [[Development/OpenOffice.org_Building_Guide]])
* [http://thread.gmane.org/gmane.comp.openoffice.devel.documentation/3231/focus=26592 Rework build documentation] (see results at [[Documentation/Building_Guide]])
== Tracking project progress ==
== Tracking project progress ==

Revision as of 17:09, 30 July 2009

General documentation about the build environment is here. This page is about the effort to improve our build environment we have just started. The complete build environment and accompanying processes and infrastructure are on trial. The results of this evaluation, discussions about them, a roadmap for future changes and milestones of past, present and future (or links to that) will appear on this page. As we didn't have a better idea, we just called our project "Build Environment 2.0".

About the project

With the preparations for our switch to a DSCM in mind and responding to all the problems in our daily work, we founded a team that will create a new build infrastructure for everybody working on OpenOffice.org. The team consists of (in alphabetical order)

  • Mathias Bauer (Project owner)
  • Hasan Ilter (QA)
  • Hans-Joachim Lankenau (Releease engineering)
  • Björn Michaelsen (Development)
  • Jens-Heiner Rechtien (Release engineering)

Everything around the project "Build Environment 2.0" will be documented in the wiki, including work in progress, discussions etc. Our plan is to define the "customers" of our build infrastructure, understand their requirements and working styles and try to find the best balance between them.

Activities already ongoing or finished

At the start of this project, it makes sense to list changes that already on their way, partially started long before this project. Some of them match the scope of this project, others can be used to base future work on.

Tracking project progress

Personal tools