Hi Eric,
Eric Hoch a écrit :
Hi Eric,
Am Mon, 3 Mar 2008 06:45:47 +0100 schrieb eric b:
This is Mac development. It's not a build issue but it's a memory leak on the
Mac for the OOH680_m6 build.
Well, what about start a new thread with a correct tiltle then ? ( the
current leads to confusion, and everything is crossposted .. bouh .. )
We should figure out why it's here, if we can fix it for 2.4.0 and if we can't fix it if it at least does not any harm.
IMHO, the best is file an issue, attribute it to macport, and find
someone to fix it :-)
If it's a showstopper or not may be discussed on qa-dev - that's right. But for now I think that the Mac mailinglist is the right
place.
I wonder why ? For me the QA arrives after development in the workflow.
( excepted child workspaces QA, and integration of course )
As discussed and agreed with Andre Schnabel (privately), -what I mean is :
1) Mac port (developers, including me) decide whether the development is
enough advanced.
Means " developers think starting one milestone, everything is ready for
release"
-> this is discussed during Mac OS X port IRC meetings.
FYI, recently, Philipp Lohmann, Stephan Schaefer and myself and some
other devs, agreed it was the case.
Exactly, it was told that, starting m300_m2, Aqua version can start to
be QA'ed (more exactly: once aquafilepicker02, aquavcl05 and maybe
nativeprintdlg01 will be integrated)
... now QA for locales starts, not before.
2) Then the Mac versions (both PowerPC/Intel and X11/Aqua) are built in
"production" and QA is organized by QA Team.
Everything in coordination with NLC. Means: QA Team does verify nothing
is wrong, following rules, using the Sun thing and so on
3) After all tests, NLC _decides_ whether a locale is ok or not for release.
(BTW: there is a mess with en-US locale, because there is no en-US
project, and en-US is default ??)
I have not the prefect solution, the discussion is open ent my opinion
is : things are simply unclear, and must be clearly defined.
But I do insist, the only QA I see with Mac OS X port development is
about Child workspaces and specs validations.
Kind regads,
Eric
--
qɔᴉɹə
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
