Could you shed some light on this? What's the current policy for
nominating / holding back childworkspaces?
as you might have seen, the integration of the warnings01 child
workspace caused some trouble in two aspects:
1. it caused some more P1 issues for some build configurations, see
fixes
Martin,
Could you shed some light on this? What's the current policy for
nominating / holding back childworkspaces? In 'releases' you announced a
'code freeze' date, but that's not reached yet.
http://wiki.services.openoffice.org/wiki/OOoRelease204
Rüdiger
Jens-Heiner Rechtien wrote:
Hi C
On Tue, 2006-07-04 at 04:52 +0200, Stefan Taxhet wrote:
>
> > I'm a little worried about how long it's taking my workspaces to go
> > anywhere
>
> Oops, they were still active?
> I found xalanupgrade and fpicker6 and moved those to the new area.
Excellent, thanks for finding them :-)
C.
---
Hi,
Caolan McNamara wrote:
I'm a little worried about how long it's taking my workspaces to go
anywhere, and I'm wondering if this is normal both for external and
internal workspaces, i.e. today is Jul 3 and I've 4 unintegrated
workspaces which are out my hands.
xalanupgrade "ready for qa" s
Hi Caolan,
you are not alone with this, check for instance encupfix01, soldep1,
perftest03, hr33 and a few others. QA was very busy with OOo-2.0.3, so I
think that's understandable. As for the approved but not yet nominated
CWSs, that's mostly due to warnings01 which just due to sheer size hol
I'm a little worried about how long it's taking my workspaces to go
anywhere, and I'm wondering if this is normal both for external and
internal workspaces, i.e. today is Jul 3 and I've 4 unintegrated
workspaces which are out my hands.
xalanupgrade "ready for qa" since May 5 => 59 days unchanged
