incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 119927] Aoo 3.4.0 clis dll are not backward compatible with ooo 3.3.0, 3.2.1 and lower
Date Sat, 16 Jun 2012 00:38:18 GMT
https://issues.apache.org/ooo/show_bug.cgi?id=119927

--- Comment #6 from Ariel Constenla-Haile <arielch@apache.org> ---
(In reply to comment #5)
> Ariel I feel you are not really interested to hook in this issue 

Please note that I didn't assign this issue to myself, it is assigned to the
AOO issues mailing lists: every new bug and every comment is read by all the
people subscribed to this list, including developers.

And it's not that I'm not interested in seeing this solved, it's simply that
I'm a Community contributor, contributing in my spare time (the @apache.org
means just that I'm a committer, nothing else; but I'm not being payed to work
here, I do it just for fun :) ).

> or I smell it requires a lot of work to do this, anyway, 

I guess it requires a lot of work even trying to verify the bug; you should
have noticed this, as you did a tremendous job setting up several Virtual
machines to test the bug - thanks for effort, by the way. Also notice that my
only contact with Windows is through a VM with WinXP: I develop on Linux, this
means another developer working on Windows may be able to work on this better
than I could.

> just want you to know I
> understand you do not wish to manage the previous OOo releases, at least, if
> you can maintain a compatibility for futur clis with the first AOO 3.4.0
> release, this will be awesome

I agree with you that it is an important issue if the CLI-URE is not compatible
with previous 3.* versions: the URE should change in an incompatible way only
between mayor releases, that is from OOo 2 to OOo 3, and from OOo 3 to AOO 4.

It may be productive to call the developer's attention by sending a mail to the
  development mailing list (ooo-dev@incubator.apache.org).

-- 
You are receiving this mail because:
You are the assignee for the bug.

Mime
View raw message