Hi Laurent,
Laurent Godard wrote:
Hi Peter
Thanks a lot for this detailed status
This requirement i not fulfilled from my point of view. As far as I
understand the discussion, MAC OS X build fails.
Right
This Mac issue has blocked the process
as the discussion went on delivering python or not within OOo on MacOs
and was stalled for us (i do not read every mac irc discussion logs)
things are evolving thanks to your IRC intervention
That was my idea. I am still not sure if the MAC version still blocks
the CWS. Do we have to wait for Joergs fix?
http://www.openoffice.org/issues/show_bug.cgi?id=76281
* Issues submitted by developers must provide a test case
to ensure appropriate verification.
There's no 'how-to test' provided.
mail merge tests could be used as written in python
That's OK.
the developper knows what he modified and should be able to identify
functional parts that has to be covered
@liyuan: I guess this is for you. Or am I wrong?
* All issues must have the status 'Resolved/Fixed'
Not the case.
yes
Only one issue. Only of formal character.
* All issues must be assigned to a QA members (except those only
developers can verify)
Not the case.
who has to be assigned there in IZ ? I may call for volunteers
I will be the right owner (when checklist requirements are met). Because
testing effort has to split I think I will have to create some child
issues for specific tasks.
as i understand the situation, we lack a QA representative dealing with
the various plateform building and check
Please spare both of us this polemic irony.
I'm really sorry, it was not my intention !!! Please forgive me
:-). No problem anymore. I have lots of understanding -especially for
single contributers- that they are not always happy with the OOo
progress all of the time. Same with me.
I hope I was not too harsh too. Your mail was one of the first things
that hit me in the morning after being late in the office due to Beijing
traffic jam.
with you making some 'need to clarify' statements. And now you're
blaming me for the project getting stalled?
Reall sorry Peter, this was not my intention
I'm the first to blame not following this point :(
For me the problem, after the macos one, was that no builder was
available for generating testing binaries on many plateform
Linux, Windows, Solaris and mac (being optional here, as not finished
yet). I thought proposing doing a fisrt step job for windows and linux
plateform
Ah, now I see MAC OS is an option. I always though it's one of the
special scopes for this CWS. That makes my above remark concerning the
IRC chat obsolete. I just leave there, because it's still interesting
for ongoing discussion. OK, we can proceed with the CWS and file another
issue against MAC OS porting project. BTW, are you a member of the MAC
port? If not, that may have been my major misconception.
The CWS process only requires testing on Windows and one other platform
out of Linux, Solaris Sparc or Solaris x86. But, we might have a special
case here, because of the involvement of Python being a third party
product. Maybe Joerg or some other experienced developer reading this
(hope they hadn't give up due to length :-)) can give some insight here.
Some information about the role of the QA representative:
- QA Rep. is not in charge to build the source
(This would be even against the idea of the CWS process)
This is where i was wrong and I'm really sorry
ho is in charge of building on many plateforms ?
Here in Beijing we can do Windows and Linux, which (see above) might be
enough. I know only Sun in Hamburg that could build Solaris if needed. I
can ask somebody there. I've been working for more than five years with
them.
- QA Rep. organizes the QA effort of a CWS
- QA Rep. doesn't organize the whole CWS process
- QA Rep. is not necessarily in charge of doing all the testing
So thanks for pointing the QA missing points
No problem, my job.
Do you think once ready for QA we should post on QA list for calling
volunteers ?
I first wait for replies on this mail. I can take care about this later.
For the last item, this is even not possible for me. Because I have no
MAC available. I will ask Jogi from Sun in Hamburg to do this part.
(BCCed him.)
Ok ! We may find also other volunteers on mac platform
what about solaris ?
As stated above, depends on Windows + Linux testing sufficient to get
the job done.
Once again peter, please forgive me for my misunderstandable words
I really hope things are clear now
Yes. Do you join OOoCon in Barcelona? I hope my company sends me. Maybe
we could meet there.
@liyuan : please look at comment in the issue about deprecation. only a
suggestion
Good idea.
once all is ok (tinderbox do not show any build error on this cws ?),
peter let us know what action you need at QA level (find ressources aso
...) - maybe on QA list ?
We'll see next weeks. Hopefully there'll be some more replies then.
Best regards
Peter
