Am Montag, 27. Mai 2013 um 18:58 schrieb janI: > On 27 May 2013 17:17, Jürgen Schmidt <jogischm...@gmail.com> wrote: > > > Hi, > > > > I would like to discuss our further schedule towards AOO 4.0 and the > > problems I see. And I would like to discuss a proposal how to address > > these problems. > > > > We are behind our schedule a little bit and we have identified some > > problems regarding the 64bit port on MacOS that I will try to explain > > below (hopefully without too many technical details that everybody can > > understand it). > > > > Proposal > > ======== > > - Move MacOS 64 bit version to 4.1 and merge stlport relevant changes > > (all platforms) asap into trunk and include them in AOO 4.0. > > > > - Move into showstopper mode next week, beginning with June 3th. Means > > we integrate only showstopper flagged issues and new translations. And > > potentially new art work if we get a new logo and icons in time. > > Deadline for new art work should be June 10th. > > > > I understand your motivation and will not be the showstopper. but my > honest opion is that the reasons for calling it 4.0 get very thin. > >
it's ok to have different opinions but let me explain why I think it's worth a new major version. The sidebar in the form we introduce with the next release is a big UI change, very visible to our users. This kind of changes should be made for major releases only. > > Getting a 64 bit release for mac (and possible in linux) is something (as > you write) for a major version and not a minor version like 4.1. > > Ariel pointed already out that Linux is not relevant here and we support a 64bit version already. As I tried to explain a 64bit version on MacOS is comparable to a new platform, a complete new port and that is possible to every version. > > I am against (but will vote -0) of making a release just to hold the > deadline, I would very much prefer to see what a realistic deadline would > be. > > It is not only to hold a deadline, it is of course time for a new release and we have a lot good stuff in it. How long do we want to move if we would move at all? 2 weeks, 4 weeks or 2 month? What would it change during the summer and vacation time? I believe not really much and we would potentially have only some further bug fixes and maybe the 64bit MacOS version. I prefer of course to give our users the new sidebar as soon as possible and receive feedback to make this feature even more shining in a 4.1. Juergen > > rgds > jan I. > > Ps. You do a great job as release manager, but someone has to be "devils > advocate". > > > > - Intensive QA with the stlport changes to detect potential problems > > > > - Create a AOO 4.0 branch 1 week later, June 10th, where we hopefully > > have integrated already returned translations. > > > > - Translation deadline will be set to June 14th to have some time for > > the integration and further testing. Further translations can we release > > at a later time as a special language update release (TBD) > > > > > > > > I would still like to keep the end of June date because everything else > > looks quite nice and we should give our users the new sidebar. > > > > A shifted release date won't really help us because we will move in the > > vacation time and I think it is better to bring the 4.0 version out before. > > > > Once we have solved the mozilla problem for the 64bit version we can > > decide if we want release a 4.1 immediately or later together with > > further improvements, fixes and further languages. > > > > > > Background Explanation > > ====================== > > > > Herbert did a great job with his ongoing work to port AOO to 64bit on > > the MacOS platform. This work is mainly triggered and motivated by the > > deprecation of some system abi's and the drop of 32 bit Java. In short > > we switched to the clang compiler, a new platform SDK, XCode4, replaced > > for example atsui API with CoreText, get rid of stlport (on all > > platforms) and did many more cleanup that work that were necessary > > because of better and/or different compiler/linker behaviour or error > > messages etc. Everything looked quite well until we focused on the still > > used precompiled older Mozilla libraries. We currently struggle with > > porting this stuff to 64 bit and evaluating if we can get rid of them > > completely. A complete drop of the mozilla libs would be a further huge > > improvement but it is of course a lot of work to understand the code > > first and all dependencies and to replace it with some new code... At > > the moment we see this on risk for AOO 4.0 and plan to postpone this to > > 4.1. > > > > But the drop of the stlport lib is relevant for all platforms and will > > introduce a binary incompatibility. The best and only time for such an > > incompatible change is a major version. The plan is to extract the > > stlport relevant changes and merge them on trunk asap (this week). This > > will decouple any further work on the 64bit port and we can release the > > 64bit version at any time later (as 4.1) because the 64bit version is > > based on a completely new platform on MacOS additionally to the existing > > one. > > > > The 32bit version will be part of the AOO 4.0 release and we will need > > this version for backward compatibility on older system anyway. The > > 64bit version will run on 10.7 and newer only. > > > > > > I am looking forward to any constructive feedback or concerns. > > > > Juergen > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > >
