RC1 of 2.4 is now available on the mirror sites.
In this package any Base user with reports created under the Report
Builder will find it is quite impossible to edit these. If they create a
new report and save it, they again will be unable to to open this file
for editing. - and it was reported, prior to the package be
disseminated. See Issue 86031 ( MAY says that report builder files have
a problem but closes the issue anyway.. ???.)
I can understand a development build going forward like this - but the
term "Release Candidate" should have some meaning and I fail to see how
that meaning can be applied in this situation.
If it is a case of the "1 bug per Issue" policy - e.g. Issue 86031 was
about Report Wizard generated reports and therefore even if Report
Builder reports are noticed to be effected also it doesn't matter, close
it anyway then that policy needs to be looked at carefully. If a matter
of expediency, eg. the file is built so it must be shipped - then again
that is a judgment call that should be re-examined for future situation IMO.
Sincerely
Drew Jensen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
