On Sat, Feb 9, 2013 at 4:35 PM, Dennis E. Hamilton <orc...@apache.org> wrote: > Thanks for adding this. > > I have added a "Calc and OpenFormat Support" subsection there, > with description of the proposed change to have POWER(0,0) produce > an error value (#VALUE!) instead of 1, the current result. That > is explained on the Release Notes and at the Bugzilla Issue #114430 > at <https://issues.apache.org/ooo/show_bug.cgi?id=114430>. >
Thanks. I'll plan on editing this down when we get closer to the release, and before we translate them. IMHO Release Notes should be succinct and to the point. For example, instead of 5 paragraphs on the topic, I would simply say: "POWER(0,0) returns the #VALUE! error. Previous versions returned 1. See Bugzilla Issue #114430." If the reader wants more details they can find them in the linked BZ issue. But out of sympathy for the eventual translators, let's keep the Release Notes succinct. -Rob > - Dennis > > -----Original Message----- > From: Rob Weir [mailto:robw...@apache.org] > Sent: Saturday, February 09, 2013 09:40 > To: dev@openoffice.apache.org > Subject: Changes that Impact Backwards Compatibility > > I've added a new section to the 4.0 Release Notes for tracking changes > that impact backwards compatibility: > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Notes > > This would include changes to the public interfaces of AOO, including > incompatible changes to API's (including spreadsheet functions), file > formats, etc. > > I think we all acknowledge that a major release like 4.0 is an > opportunity to make incompatible changes, but I hope we also agree > that this is not a free-for-all where we can indiscriminately break > compatibility. We need to think carefully about where we break > compatibility, have good reasons for it, and have a plan for how we > communicate such changes to users and application developers. The > later, especially, need advance notice. > > Personally, I consider any changes that break compatibility to be > "controversial" and think that lazy consensus should be sought on this > list before committing it. > > Regards, > > -Rob >
