LibO version 4.3.0 released. Is it bitwise identical with RC4?

Just noticed that now is offering 4.3.0 as the current version.

  1. As I recently downloaded RC4 I would like to know whether or not the released builds are bitwise identical with RC4.

  2. Having just found a bug in RC4 I have to decide whether a report about it makes sense. Wanted to do it without a second fresh install within a couple of days.

(Running on Win8)

Yes, the official release is EXACTLY the same as the final Release Candidate (in this case RC4)

It always makes sense to report a confirmed/repeatable bug. If this bug appeared in RC4 but wasn’t present in RC3 then it is a clear regression and has (or should have) higher priority.

That said, users should NEVER use an x.x.0 release for critical work. At this moment it is wiser to stay with the 4.2 branch.

Thanks @Pedro1 ! I remember cases where what you say was explicitly printed on the official page. This time not. RC4 was the only RC for 4.3.0 I tested. Thus I cannot tell anything about a possible regression. If you are ready to try: There are array expressions only returning a single value (arrays INTERNAL). Filling down such a formula will result in copies without the array property (signalled {}) and working non-array as displayed. Filling ‘Down’ for just 1 step does work correctly. Fillng to the ‘Right’ (also by dragging) is ok. Anybody same observations? (Win8)

@Lupp, can you please create a Bugzilla issue with step by step instructions (and a sample file if that makes sense)? I am not that familiar with arrays to understand what the problem is…

@Pedro1 : Maybe, I can. But I really don’t like it. Of course, it’s nonetheless my turn, I agree.

@Lupp, maybe if you through the Bug Submission Assistant (also known as BSA…) it is less painful? :slight_smile: