Hi Andre,
the best way to address showstoppers is to file an issue and report the
issue number on releases. It may be useful in some cases also to explain
the reason for reporting an issue as a showstopper,
Martin
Andre Schnabel wrote:
Hi *,
well .. the subject already tells the question:
what is the correct way to address showstoppers?
As said, we found at least one issue in 1.1.5rc, that is heavy enough to
stop the release (that means at least the current german localized 1.1.5rc
won't get a GO).
But how should we address it? ATM it is not possible to file an issue with
correct information (cannot set 1.1.5rc as version number). Furthermore to
me, such issues need to be addressed (and fixed) immidiately. If the issue
was filed, it became a P1 issue, as it it breaks the testtool environment
for the multiuser installation. (So proper testing is not possible).
At the other hand, we should not become headless and first go through the
issue and try to identify the real problem. What means .. this would take
some time for investigation.
So .. any ideas, how to proceed?
I ask, because germanophone team would like to go on with release testing.
But we are used to test "only" the localization (that's, wath we have been
more or less been told). But this time, english RC's seem to be affected as
well. So .. what should we do? Should we wait for the next localized RC's?
Should we rather try to organize more extensive community qa for the english
RC?
andré
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
