Hi Pavel,

Pavel Janík a écrit :
   From: Eric Hoch <[EMAIL PROTECTED]>
   Date: Mon, 25 Apr 2005 16:14:36 +0200
   > - Next decision to be made is: Who does the official build for Mac OS

We are not yet ready for end-users anyway, so why talking about "official"

"official" is a bit clumsy, here. Simply decide who does what is now necessary. It's time, IMHO.


builds? Let's concentrate on real work and do not talk about meta-work.

:-) It's not meta-work. the exact word I'm thinking is *synergy*.

We now need to organize Mac OS X port.

And for organize, a serious Roadmap, or jobs or whatever word you want *must* be decided : we now are ~ 8 to 10 to work around Mac OSX port, so it's necessary.

Actually, we have no synergy.

If there are issues in MacOS X builds (and I do not care if maho's or
Eric's),

Me not : it's QA too to have at least 2 builders...

 they should be reported. How many issues we have?

For 1.9.xx, searching with simply "Mac OSX" word, and if I'm not wrong, I found :

[Owner / issue ] :

1) easy to fix
maho <http://www.openoffice.org/issues/show_bug.cgi?id=46963>

2) needs more work, not trivial  *important issue*
ericb <http://www.openoffice.org/issues/show_bug.cgi?id=47888>

IIRC, duplicate of  #i47888# :
bc <http://www.openoffice.org/issues/show_bug.cgi?id=48186

3) to be confirmed (probably invalid)
ericb <http://www.openoffice.org/issues/show_bug.cgi?id=48148>

4) for debug purpose only :
ericb <http://www.openoffice.org/issues/show_bug.cgi?id=47112>

5) accented chars in filenames and dirnames
ericb <http://www.openoffice.org/issues/show_bug.cgi?id=44530>

6) Packaging *is important* on Mac OSX
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=42996>

7) Sound does not work in galery or in impress transition (same problem)
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=48216>

8) libiiop_uno.dylib is mising after install
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=48219>

9) probably one or two major issue not known at this time.
...

+ last but not least, a cws called macxjoin1993 will contain a lot of other fixes, but we have to discuss with Patrick Luby the content. No hurry yet.

That's all what I know for 1.9.xx, so the answer is :

We currently have *yet 9 issues* at least to solve


I think that m98 could be a milestone for us.

I think so, only and only if #i47888# is fixed.

About 1.1.4 -> 1.1.5, everything will probably be included in maxjoin1553 concatened with :

[Owner / issue ]

1) xmlsec and berkeleydb prototype :
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=37733>

2) libdb_java-4.2.dylib missing / not build
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=38031>

3)locales (fr/de/ja):
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=46633>

4) accented chars in filenames and dirnames
ericb <http://qa.openoffice.org/issues/show_bug.cgi?id=46635>

5) sound for OOo1.1.4 with Mac OSX
ericb  <http://qa.openoffice.org/issues/show_bug.cgi?id=46637>

For all : *PLEASE* wait and dont create a cws fr 1.1.4 on Mac OSX before to ask... It's not a good idea to commit the changes twice (with maxjoin1553, or others...)


It will (probably) contain
all fixes from macosx06 and pj26, so we should have the main patches merged
in and stabilize our build systems a bit.

Yes, we're close to the first point I told...


I'll continue to build for MacOS X for the languages we support in our
build systems, because our builds contain localized stuff and more and our
teams would like to use the same source for all platforms (GNU/Linux,
Windows, Solaris and MacOS X) thus making the QA much efficient and share
the QA results between various teams (because of the same core binaries).

From my side, I'd prefer learn the code, and most important Cocoa.


Regards, eric bachard



--
eric bachard <[EMAIL PROTECTED]>
Francophone OpenOffice.org Commmunity developer (Linux PPC / Mac OS X / X11)
See : <http://fr.openoffice.org>



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to