ReleaseStatus Minutes 2011-04-11 IRC log

(14:59:18) #oooreleases: The topic for #oooreleases is: Release-Stauts-Meeting, every monday at 15:00 Hamburg Time (13:00 UTC in summer)
(14:59:20) mla: hi
(15:00:13) of_oracle: Hi
(15:01:42) mdamboldt: Hi
(15:01:51) mdamboldt: Welcome to todays release status meeting.
(15:02:21) mdamboldt: The OpenOffice.org 3.4 Beta release is just around the corner.
(15:02:39) mdamboldt: Upload and distribution thru the mirror network is in progress.
(15:02:57) kai_a [~kai_a@188-193-189-22-dynip.superkabel.de] entered the room.
(15:03:16) mla: also the announcement is (as draft) prepared, so we should be able to release tomorrow
(15:03:18) mdamboldt: Draft announcement has been published on pr@marketing mailing list
(15:07:42) mdamboldt: All in all we are in good shape for the 3.4 release but there is still a couple of work ahead when looking at current issue numbers. There are still about 10 open regressions and around 110 on 3.4 target in general. Those need to be addressed asap to get into "release ready state". Which means <= 3 open regressions as announced a couple of weeks ago by Martin Hollmichel at http://blogs.sun.com/ratte/entry/some_changes_for_the_openoffic
(15:07:42) mdamboldt: example.
(15:08:46) RBRACONI [~chatzilla@nat/sun/x-ofesfojjmekmyhrf] entered the room.
(15:09:30) mdamboldt: One of the very good news is, that nearly all of those issues which have been raised as important candidates for a next release (3.3.1 talks on the mailing list) have already been addressed and fixed in the current milestone. Thus they are fixed in the 3.4 Beta release.
(15:09:54) RBRACONI is now known as rafaella
(15:10:33) mdamboldt: As usual I've created a new meta issue for the 3.4 release. It's issue 117745.
(15:10:38) IZBot: code P2 OOo 3.4 release stoppers / blockers http://openoffice.org/bugzilla/show_bug.cgi?id=117745
(15:12:36) mdamboldt: Please raise stopper candidates as usual on the releases mailing list. (in case they don't already match the release criteria - e.g. being a regression, data loss, etc. which would obviously need to be fixed on 3.4 target)
(15:13:41) mdamboldt: I think thats all I've for todays meeting.
(15:13:43) mdamboldt: Anything else?
(15:14:05) of_oracle: Not from my side.
(15:14:21) stefan_b: no
(15:14:34) mla: Just a hint that we took the milestone DEV300m106 for the OOO340 branch off
(15:14:45) mdamboldt: ml1: good point!
(15:19:30) mdamboldt: Another thing: To calm the OOO340 code line down a little, we will switch to longer milestone cycles on the way to the 3.4 release. For now these will be three week cycles as already mentioned at http://blogs.sun.com/ratte/entry/some_changes_for_the_openoffice. So in case you are addressing further 3.4 issues and you are eager to get early feedback from submitter of an issue or whom ever, please use the established and well known metho
(15:19:31) mdamboldt: like qa-upload (FTP) to provide separate CWSs / patches for early feedback on fixes.
(15:20:59) mdamboldt: By this you should be provided by early, dedicated and quality feedback.
(15:21:05) msc_oracle left the room (quit: Ping timeout: 240 seconds).
(15:21:49) mdamboldt: Thats all I've for today.
(15:22:57) mdamboldt: So happy Beta testing and don't miss to provide your feedback!
(15:22:58) mdamboldt: bye
(15:24:33) mla: bye