Difference between revisions of "BuildBot Meeting"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) |
|||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | == Meeting 19.12.2007 9:30 AM Hamburg Time (UTC+1) == | ||
| − | + | ===IRC channel for this first meeting will be #unhack-oo on freenode.net=== | |
| − | + | ||
| − | == | + | |
| − | + | ||
| − | channel for this first meeting will be #unhack-oo | + | |
=== Agenda === | === Agenda === | ||
| − | |||
| − | |||
| − | |||
# create new Mailing list or use tinderbox@tools.openoffice.org? | # create new Mailing list or use tinderbox@tools.openoffice.org? | ||
# create a new IRC channel. something like #OOO-buildbot | # create a new IRC channel. something like #OOO-buildbot | ||
# When will the next meeting take place? | # When will the next meeting take place? | ||
| + | # Should there be more than one Buildmaster? | ||
| + | # ... | ||
| + | # what issues have to get addressed to have a working process and who will address them | ||
| + | #* issues about the buildbot | ||
| + | #** how can maintainance be reduced. Update of scripts, centralized patches for milestones, known broken milestones, finished tagging triggers first builds of the next milestone | ||
| + | #** allow handling of multiple instsets | ||
| + | #** usability: have the "Branch to build" / "Revision to build" fields renamed /removed | ||
| + | #* issues about other needed infrastructure | ||
| + | # ... | ||
# Q&A | # Q&A | ||
| + | |||
| + | |||
| + | Logfile: [[Media:Buildbot_Meeting_at_FreeNode-unhack-oo_log.odt]] | ||
| + | [[Category:Build System]] | ||
Latest revision as of 16:53, 31 January 2010
Meeting 19.12.2007 9:30 AM Hamburg Time (UTC+1)
IRC channel for this first meeting will be #unhack-oo on freenode.net
Agenda
- create new Mailing list or use tinderbox@tools.openoffice.org?
- create a new IRC channel. something like #OOO-buildbot
- When will the next meeting take place?
- Should there be more than one Buildmaster?
- ...
- what issues have to get addressed to have a working process and who will address them
- issues about the buildbot
- how can maintainance be reduced. Update of scripts, centralized patches for milestones, known broken milestones, finished tagging triggers first builds of the next milestone
- allow handling of multiple instsets
- usability: have the "Branch to build" / "Revision to build" fields renamed /removed
- issues about other needed infrastructure
- issues about the buildbot
- ...
- Q&A
Logfile: Media:Buildbot_Meeting_at_FreeNode-unhack-oo_log.odt
