Here we go again.....
eric.bachard wrote:
Hi Maho,
Maho NAKATA a écrit :
Hi
DEV300_m21 has been provided, and if you have serious problems i
think I can add some notes in my announcement at release@
No, let's talk here : this is Mac development list, and here is the
place where things have to be discussed.
One problem is you ignore whats happening on this list, and you don't
test the builds you are providing.
When there are problems (like now), this is bad for the image of the
Aqua version : the users started to complain, and what one need years
to build, just needs several days to be broken.
Eric, Maho has NEVER tested his builds to my knowledge. That is what
the QA testing team is here for. Maho fixes problems he encounters with
the build process.
That's even the reason why I decided to provide my own unofficial and
hacky builds including fixes on http://oooaqua.laurentbuisson.fr
Wonderful that you do this. Once your builds work, then it is time to
build a CWS and get your fixes into the Master build process.
IMHO, you should limit the number of builds you provide, to the builds
for to-be-QA'ed-releases or, from time to time technical preview, on
mac developers requests, because they really know the existing
problems, and can say if an official milestone has to be public or not.
Maho should only limit builds if good-day.net is running out of space or
builds are released very close to each other, which indicates there was
a problem with a release. This has happened several times.
or, you can post a message as well.
To be constructive, my proposal is :
- you provide firstly the to-be-QA-ed-builds: even if they are buggy,
any important bug/issue is P1 or P2
- you provide some developer snapshots, *on Mac porters requests*, for
the visibility of the progress
Why should we wait on 'Mac porters request'? It takes at least a day
for all of the builds to finish. Also, SUN is providing builds of the
DEV300 milestones for each release.
- the devs do provide developers builds, unofficial and hacky, for
their testers because they know what they do
No. Developers build to fix bugs. Once the bug is fixed, they create a
CWS to put the fix into for QA. QA acknowledges the release and
retrieves the build and tests it for both the fix and any regressions.
If the CWS meets BOTH requirements, the CWS is released to be placed
into the Master build line. No 'hacky builds' that have MY code.
Unless you want to support your own builds or if you are requested to do
a build, as I have on several occassions asked you to do so.
http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/Dev_DEV300_m21/
I'd suggest you to remove them. Please ask and wait for the "ok" from
mac porters before to provide a new one (probably DEV300_m24)
Why? Is there a P1 issue that exists solely for the Mac OS X port?
Then identify it, fix it and get a CWS together so that the fix may be
incorporated before 3.0 is released. Otherwise, Maho is doing what he
said he would do and I, for one, would not want him to stop.
BTW, have we NOT been down this road before?
James McKenzie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
