Mailinglist Archive: opensuse-buildservice (206 mails)

< Previous Next >
[opensuse-buildservice] Build Team Meeting
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Tue, 17 Mar 2009 15:11:04 +0100
  • Message-id: <200903171511.05035.adrian@xxxxxxx>

present: froh, mls, freitag, abauer, rlihm, adrian, cwh

Topics:
* Status round
* 1.5 release
* Infrastructure
* Test Development System

Status round
============

freitag:
* Working on Hermes, fixed bugs and created new :)
* Got rid of locks in hermes

abauer:
* Improved Web Client:
- Sub projects are visible in project page now
- Improved project page loading time for large projects via
delayed loading of build results.
both is already active on build.opensuse.org
* Thinking about rights management of property system.
Not final thought, but updated wiki page.
* Implemented meta forwarding for remote projects in frontend.

rlihm:
* web client css fixes for new version.
* Discussion how to move the templates into development.

adrian:
* Presented openSUSE and Build Service at Linuxtage Chemnitz
AI: adrian create fate request for STABLE/Development classification.
( #306323 )

mls:
* working on link repair support in source server
* fixing osc build for a local build service
* implemented meta forwarding for remote projects in backend.


1.5 Release
===========
* planned 1.5 release is this thursday.

Infrastructure
==============
* download/stage.o.o hardware failure
* power outage for build hosts for one night
* source server problem on sunday, unknown reason for now.
* Binary backend server has reached it's limits. Our general purpose backup
system will replace it after a memory upgrade.

Test Development System
=======================
* Klaas will take a former build host and get it installed and reachable via
one public IP address for testing and development purposes.


--

Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx


--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >