Difference between revisions of "ReleaseStatus Minutes"
Paveljanik (Talk | contribs) (→Agenda for 2007-01-29) |
|||
| Line 4: | Line 4: | ||
* review of issues with 2.2 target | * review of issues with 2.2 target | ||
| + | * macosxmapfiles approval/diapproval for 2.2 | ||
== 2007-01-22 == | == 2007-01-22 == | ||
Revision as of 09:57, 28 January 2007
On every Monday 3pm German time there is a meeting (#oooreleases on irc.freenode.net) to review the status for the next releases.
Contents
Agenda for 2007-01-29
- review of issues with 2.2 target
- macosxmapfiles approval/diapproval for 2.2
2007-01-22
Participants: Joost Andrae, Mathias Bauer, Pavel Janik, Bettina Haberer, Martin Hollmichel, Uwe Luebbers, Heiner Rechtien, Ruediger Timm, partly Noel Power,
RE this week: SRC680 obo, OOF680 kz
issue tracking
- 59 open issues for 2.2 target
- still 15 open new cws for 2.2, there are only 4 days left before code freeze.
- cws npower5: probably reschedule for 2.3
- review of OOoRelease221-timeline, this is a regression bugfix release only, issues for this target milestone will be reviewed by this team.
- review of OOoRelease23-timeline, Feature Freeze will be on July 5th.
2007-01-15
Participants: Joost Andrae, Mathias Bauer, Pavel Janik, Bettina Haberer, Martin Hollmichel, Heiner Rechtien, Ruediger Timm, Thorsten Ziehm
RE this week: SRC680 vg, OOF680 rt
issue tracking
- more than 150 open issue for 2.2 target
- more than 50 open cws for 2.2, there are only 10 days left before code freeze. We need to reduce to much less than 25 cws beginning next week otherwise we will run into problem with the last integration for code freeze.
- retarget of these cws will be done: ab33, calcwarning, mingwport03, asyncdialog2, unxlngs06, buildjars.
new strings in os91
Writer Format->Bullets & Numbering has many unaccessible components There are missing strings (24) for making this functionality not usable in a11y context. There are not visible in normal context, but are considered as stopper for a11y for the release. We accepted this as an exception for late integration. A Heads up will be send out to dev@l10n.
2007-01-08
Participants: Joost Andrae, Mathias Bauer, Pavel Janik, Martin Hollmichel, Uwe Luebbers, Heiner Rechtien, Ruediger Timm
RE this week: SRC680 vg, OOF680 rt
issue tracking
- more than 200 open issue for 2.2 target
review of cws with target 2.2
- freeafms: this cws changes afm files, the consequences are not fully known yet, we need some more time for evaluation, UweL to use convwatch for justification -> retarget to 2.3.
- lfs: still open -> target 2.3
- openbsd01: ongoing porting work -> target 2.3
- splashperform: due date Feb 20th -> target 2.3
- adc7: MH: ask Nikolai about requirement for 2.2
- languageguessing: unfortunatly missed the Feature freeze deadline -> target 2.3
- cppuhelpshrink: will revisit next week to see if all open issues have been resolved
- kaib01: -> seem not to be releavant for 2.2 -> target 2.3
2006-12-18
Participants: Pavel Janik, Martin Hollmichel, Louis
RE this week: SRC680 ihi
issue tracking
- more than 250 open issues for 2.2 target
- we will introduce 2.2.1 and 2.3 in IssueTracker and EIS
new Release model
- last version of new Release model we agreed on is available on Release_Model
2006-12-11
Participants: Joost Andrae, Mathias Bauer, Bettina Haberer, Martin Damboldt, Pavel Janik, Heiner Rechtien, Ruediger Timm
RE this week: SRC680 kz (Kurt Zenker)
2.1.0rc2 has been decided to be 2.1 final last friday. The builds for en-US + source tarballs + SDK have been hard linked to 'stable'. Website changes for 2.1 release will be done tomorrow. PR needs to be involved. Solver tarballs currently build and will be uploaded later (probably Thursday)
issue tracking
- There are currently 8 open CWS targeted for OOo 2.2 that contain UI changes. One of them (ab31) might miss timelines.
2006-12-04
Participants: Joost Andrae, Mathias Bauer, Bettina Haberer, Martin Hollmichel, Pavel Janik, Heiner Rechtien, Ruediger Timm
RE this week: SRC680 rt
issue tracking
- no more open issues for 2.1, still looking for more feedback on rc2
- rc2 is out sinceDecember 1st, we will decide on Friday, December 8th, after a week of feedback, about this rc will being the final, so
- new estimated release date will be: Dec 12th
- more than 200 open issues on 2.2 target, UI/Feature freeze will be in about three weeks (December 28th). Most of Sun stuff will be ready a week earlier because of christmas break.
- AI Martin H.: write up summary of new proposed release model and post it on releases@openoffice.org
2006-11-27
Participants: Joost Andrae, Mathias Bauer, Bettina Haberer, Martin Hollmichel, Pavel Janik, Uwe Luebbers, Heiner Rechtien
RE this week: SRC680 rt, OOE680 obo
issue tracking
- no more open issues, still looking for more feedback on rc1
- rc2 planned for December 1st, pb19 and ft2109mono cws with stoppers
- new estimated release date: Dec 12
projects
changed approval process for child workspaces in EIS
effective with next Wednesday (November 29th) we will introduce a more open approval process:
For a release (like 2.1 in the moment) Project Leads of the accepted projects and the member of this team are able to nominate child workspaces. In detail this means that any project lead is able to nominate any cws.
For a development snapshot (2.2 in the moment) QA representatives do not approve child workspaces any longer, but nominate them directly.
splitted source tar balls
Joost works with kendy to make the script also working on Solaris and will start providing them
more full installation set for more languages
In the moment we are not able to provide more "full" installation set for new languages (see Vietnames request on releases) because of diskspace constraints. They were also some concern to extend this list endless because this don't scale at all. Providing full installation set means big redundancies within the packages because the languageindependent are the most of full installset.
2006-11-20
Participants: Joost Andrae, Mathias Bauer, Martin Hollmichel, Pavel Janik, Uwe Luebbers, Heiner Rechtien
RE this week: SRC680 ihi, OOE680 obo
issue tracking
- 9 open issues for OOo 2.1, most of them localization related.
- 62229 "Cannot access any resources via AFP" has been accepted as Mac-only fix for 2.1 release
- the fixes for remaining stoppers are on track, we expect approval for cws "gtkquickstart3, impress113 pb18 ppbfix tl34" by Tuesday afternoon
- that build should then be available on Thursday 23rd as release candidate for 2.1
- agreement to retarget cws "lfs" to target to 2.2 since it is enhancement and not critical for 2.1 release
- AI: pavel to review l10n issues
- AI: joost to provide new proposal for naming scheme (http://development.openoffice.org/releases/filenames.html) to adress both builds, SRC680 and OOE680, as snapshot builds
- AI all: update http://wiki.services.openoffice.org/wiki/OOoRelease205 accordingly
2006-11-13
Participants: Joost Andrae, Mathias Bauer, Martin Hollmichel, Pavel Janik, Uwe Luebbers, Heiner Rechtien
RE this week: SRC680 vg, OOE680 hr
issue tracking
- 34 open issues for OOo 2.1, most of them localization related.
- new meta issue 71255 created to track potential blocker for 2.1 release.
- added after review : 71436, 70908
misc.
- we will calm down traffic on SRC680 until aw024, which touched lot of stuff. Armin will then be able to resync a last time before integration.
- pavel will have a closer look to i70517, will also test Sun build.
- we expect to provide 2.1rc begin of next week (~ November 21st)
2006-11-06
Participants: Mathias Bauer, Martin Hollmichel, Pavel Janik, Uwe Luebbers
beginning with this meeting we will meet on irc.freenode.net (#oooreleases) on regular basis. In the mid term we would like to re-establish the release committee again.
RE this week: SRC680 kz, OOE680 obo
issue tracking
- 65 open issues for OOo 2.1, most of them new and localization related.
- new meta issue 71255 created to track potential blocker for 2.1 release.
Projects
upload of snapshots
with the parallel upload of snapshots will have problems with our current naming scheme. short term solution is to use OOE680/SRC680 in the name of the tarballs. We need to work on a new naming scheme with makes more clear the relation of the snapshots to the releases. Martin to ask Joost for a new proposal.
