Status OpenOffice.org 3.4

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Status OpenOffice.org 3.4

Martin Hollmichel-3
Hi all,

* Release status*
although we made good progress regarding the release relevant issues
(<http://wiki.services.openoffice.org/wiki/OOoRelease34#release_relevant_issues>)
for OpenOffice.org 3.4 we missed the criteria for branch off the release
branch. The biggest issue is still the amount of open regressions (we
cut that amount in half but still have more than 25 open) so that we
will do an fixing round of three weeks to achieve that goal.

* Translation status*
The DEV300_m101 build will be used to start translation for 3.4 as most
translation changes will then be integrated. During the next three weeks
of fixing the mentioned release relevant issue there will be no
integration of any new stuff, possible exceptional requests will be
handled by the release status meeting.

* next steps*
- we will concentrate fixing the release relevant issues within the next
weeks, we will review the issue status on March 7th if we are ready for
branch off.
- please do not plan to integrate new stuff or re-factor code, we are
now in stabilization phase. As the only exception I'm waiting for the
finishing svg-import cws, as this feature has been long waited for, it's
close for getting finished and it is not translation relevant.

please bookmark
http://wiki.services.openoffice.org/wiki/OOoRelease34#Detailed_schedule_for_OpenOffice.org_3.4
for the next milestones.

Martin



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [dev] Status OpenOffice.org 3.4

Stephan Bergmann-2
On 02/16/11 11:23, Martin Hollmichel wrote:
> * next steps*
> - we will concentrate fixing the release relevant issues within the next
> weeks, we will review the issue status on March 7th if we are ready for
> branch off.
> - please do not plan to integrate new stuff or re-factor code, we are
> now in stabilization phase. As the only exception I'm waiting for the
> finishing svg-import cws, as this feature has been long waited for, it's
> close for getting finished and it is not translation relevant.

Who would decide whether or not to elevate
<http://qa.openoffice.org/issues/show_bug.cgi?id=92926> "Java AWT
doesn't work (can't start)" to being release relevant?  (By the way, mh
flagged it as "RM-S3" in the "Status whiteboard"---no idea what that means.)

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [dev] Status OpenOffice.org 3.4

Martin Hollmichel-3
On 02/18/2011 12:30 PM, Stephan Bergmann wrote:

> On 02/16/11 11:23, Martin Hollmichel wrote:
>> * next steps*
>> - we will concentrate fixing the release relevant issues within the next
>> weeks, we will review the issue status on March 7th if we are ready for
>> branch off.
>> - please do not plan to integrate new stuff or re-factor code, we are
>> now in stabilization phase. As the only exception I'm waiting for the
>> finishing svg-import cws, as this feature has been long waited for, it's
>> close for getting finished and it is not translation relevant.
>
> Who would decide whether or not to elevate
> <http://qa.openoffice.org/issues/show_bug.cgi?id=92926> "Java AWT
> doesn't work (can't start)" to being release relevant?  (By the way,
> mh flagged it as "RM-S3" in the "Status whiteboard"---no idea what
> that means.)
see also my message on this list
(<http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=16599>)
explanation of these tags. So this at least that meets my criteria of
being release relecant, so if nobody objects and you say that the risk
is overseeable I would take the fix for 3.4,
<http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=16599>
>
> -Stephan
hth,

Martin

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>