| View previous topic :: View next topic |
| Author |
Message |
OPENSTEP
The One
Joined: May 25, 2003
Posts: 4752
Location: Santa Barbara, CA
|
 Posted: Tue Oct 09, 2007 9:03 pm Post subject: |
|
| Lorinda wrote: | I can't answer the question about what the plans are. But I would urge caution about moving too quickly to the 2.3 codebase. 2.3 broke printing for Base Reports and Forms. (see issue 81705). While there are some work arounds, it hasn't been fixed yet.
Seems like I saw some other pretty significant bugs/problems reported at http://www.oooforum.org but I'm not remembering them at the moment. |
This has usually been the historical pattern we've noticed with OOo as well. The 2.3 release seemed a bit rushed and didn't even have an RC period associated with it. We tend to skip these ".0" releases and wait until the actual bugfix releases which are a bit more stable.
The one break from that pattern was 2.0.3, which seemed rushed out due to some security issues and had some nasty bugs, particularly in Base IIRC.
ed |
|
| Back to top |
|
 |
Lorinda
Captain Mifune
Joined: Jun 20, 2006
Posts: 2051
Location: Midwest, USA
|
| Posted: Tue Oct 09, 2007 9:15 pm Post subject: |
|
| OPENSTEP wrote: |
This has usually been the historical pattern we've noticed with OOo as well. The 2.3 release seemed a bit rushed and didn't even have an RC period associated with it.
|
One theory metioned (more than once) in the oooforums is that the release of 2.3 was rushed in order to time the release with OOo Con 2007 in Barcelona.
Lorinda |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Tue Oct 09, 2007 10:27 pm Post subject: |
|
| Lorinda wrote: | | One theory metioned (more than once) in the oooforums is that the release of 2.3 was rushed in order to time the release with OOo Con 2007 in Barcelona. |
That is definitely my theory as well. The fact that there was no release candidate and there were several severe bugs in the new Chart and DB Report Writing code just days before release does not give me much comfort.
In any case, even if we wanted to use the OOo 2.3, we need to wait for Novell to get their ooo-build code upgraded to OOo 2.3. Since they lag behind OOo by at least a month or two, I don't there will be an ooo-build release by Novell that uses OOo 2.3 before we do the release with the features discussed at the beginning of this topic.
Patrick |
|
| Back to top |
|
|
ovvldc
Captain Naiobi
Joined: Sep 13, 2004
Posts: 2352
Location: Zürich, CH
|
| Posted: Sat Oct 20, 2007 7:53 am Post subject: |
|
I wanted to add this thread to the wiki NeoOffice and Aqua page, under the 'Development Roadmap' heading, but that page seems to be locked from editing  .
-Oz |
|
| Back to top |
|
|
sardisson
Town Crier
Joined: Feb 01, 2004
Posts: 4588
|
| Posted: Sat Oct 20, 2007 9:35 am Post subject: |
|
Updated. Thanks for the heads-up, Oscar.
Smokey
_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki |
|
| Back to top |
|
|
ovvldc
Captain Naiobi
Joined: Sep 13, 2004
Posts: 2352
Location: Zürich, CH
|
| Posted: Thu Nov 15, 2007 11:11 am Post subject: |
|
The people at OOo porting have a Quicktime for media implementation going as well. It should be at http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fmacosxquicktime01
I am not sure if it is worth a look, but the CWS is reportedly in QA now.
Also, I am wondering how progress down the roadmap is going. I have seen a lot of issues with Leopard and math equations around recently, and I have the impression that that was not expected before Leopard came out. I hope these havent been too much of a pain.
Best wishes,
Oscar
_________________
"What do you think of Western Civilization?"
"I think it would be a good idea!"
- Mohandas Karamchand Gandhi |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Thu Nov 15, 2007 11:48 am Post subject: |
|
Ed and I saw that a couple of weeks ago. I haven't tried out their code yet, but if it looks good, we'll use the same approach as we used for the Mac OS X address book code: we'll include their code, give them public credit for their work, and donate any bug fixes back to them.
Patrick |
|
| Back to top |
|
|
|
