Re: Time to push on for 4.2.0
Hi Pedro, Am 14.04.2018 um 16:32 schrieb Pedro Lino: >> Localization is, so to say, under my "ownership" (meaning: it's an area >> where I've volunteered to lead the effort); but I can't commit to >> getting it done by a certain deadline right now. Volunteers welcome, of >> course; even beginners. > I have previously volunteered to get the Portuguese version ready for release. > I am volunteering again. > Is there any work to be done on Pootle? There is always something to improve on Pootle. ;-) But that's not the point here: We need to get Pootle and the source code in sync again. After that is done, there will be *a lot* of work to be done on Pootle... Regards, Matthias > > Regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Time to push on for 4.2.0
> Localization is, so to say, under my "ownership" (meaning: it's an area > where I've volunteered to lead the effort); but I can't commit to > getting it done by a certain deadline right now. Volunteers welcome, of > course; even beginners. I have previously volunteered to get the Portuguese version ready for release. I am volunteering again. Is there any work to be done on Pootle? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Hi Andrea, Am 14.04.2018 um 15:31 schrieb Andrea Pescetti: > Jim Jagielski wrote: >> We then svn copy trunk to a AOO420 branch and >> start focusing on getting a 4.2.0 GA release out. > > On my side, this looks OK but localization is still lagging behind. > > Unless we deem it acceptable to get 4.2.0 out in English only (or with > a significant percentage of English strings in the UI even for > localized versions) this is still quite blocking, especially > considering that there is an entire localization community that will > need to be reactivated. > > Localization is, so to say, under my "ownership" (meaning: it's an > area where I've volunteered to lead the effort); but I can't commit to > getting it done by a certain deadline right now. Volunteers welcome, > of course; even beginners. You can count on me. But at the moment I am having troubles with po2oo or better how to get the en-US template. ;-) BTW: I managed to build Arabic and Ukrainian for Windows. There were problems with packaging (NSIS). I could work around it, but am still looking for a "real" solution... Regards, Matthias > > I do think we should try and get 4.2.0 out in all languages; but for a > beta it would be acceptable to have English only, or incomplete > translations. > > Localization doesn't have a big impact in terms of branches since what > we have now is not aligned to the code anyway. And localization files > live in their own directory so conflicts are not to be expected. > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Time to push on for 4.2.0
Jim Jagielski wrote: We then svn copy trunk to a AOO420 branch and start focusing on getting a 4.2.0 GA release out. On my side, this looks OK but localization is still lagging behind. Unless we deem it acceptable to get 4.2.0 out in English only (or with a significant percentage of English strings in the UI even for localized versions) this is still quite blocking, especially considering that there is an entire localization community that will need to be reactivated. Localization is, so to say, under my "ownership" (meaning: it's an area where I've volunteered to lead the effort); but I can't commit to getting it done by a certain deadline right now. Volunteers welcome, of course; even beginners. I do think we should try and get 4.2.0 out in all languages; but for a beta it would be acceptable to have English only, or incomplete translations. Localization doesn't have a big impact in terms of branches since what we have now is not aligned to the code anyway. And localization files live in their own directory so conflicts are not to be expected. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Just FYI: The Windows build from buildbot and my local build based on revision 1828829 work fine for me. Regards, Matthias Am 12.04.2018 um 19:15 schrieb Damjan Jovanovic: > I think it would take about 2 weeks for the most essential items. > > But sadly my Windows build is crashing on startup and my FreeBSD build is > crashing during the build in main/offapi due to some kind of memory bug in > idlc (either due to changes in FreeBSD or corruption of my system files), > so sadly I first need a few days to investigate and possibly reinstall my > setups. > > I'll keep you updated. > > > > On Thu, Apr 12, 2018 at 4:11 PM, Jim Jagielski wrote: > >> +1 from me. After the below would be a good time to create >> the 4.2.0-dev branch from trunk. >> >> Do you have a timeframe for the below? >> >>> On Apr 10, 2018, at 9:26 PM, Damjan Jovanovic wrote: >>> >>> Hi >>> >>> Before we start on 4.2.0 I would like to finish off porting one final >>> module, main/jvmfwk, to gbuild. Then I'll take a break from the build >>> changes, and would like to contribute these improvements: >>> >>> * Overhaul our Java support. Support newer Java versions. Enhance Java >>> detection on *nix, adding OpenJDK and matching on prefixes (like openjdk* >>> for FreeBSD, eg. /usr/local/openjdk7, /usr/local/openjdk8) instead of >> fixed >>> strings such as "jdk". Look in /usr/lib too on 64 bit Linux instead of >> the >>> RedHat-only /usr/lib64. Accelerate Java autodetection by resolving >> symbolic >>> links and caching results to avoid the slowness of multiple unnecessary >>> checks of the same Java directory through different symlinks. >>> * GStreamer 0.1 and 1.0. >>> * Audit the new SDBC-JDBC bridge and ensure it's 100% compatible with the >>> old one. >>> * Library naming and symbol versioning audit of all libraries against >> 4.1.x. >>> * Run all tests against 4.1.x and trunk, and fix the regressions. >>> * Full PostgreSQL support (views, indexes, users, groups, GUI dialogs) if >>> there is time. >>> * Get the Mediawiki plugin working again, if there is time. >>> >>> >>> On Tue, Apr 10, 2018 at 2:54 PM, Jim Jagielski wrote: >>> We have still not yet made any strategic determination... We have a possible scenario where gstreamer can be built regardless of what version the build system has in place, but, afaict, that has not yet been folded in. My suggestion would be that that gets committed ASAP so we can test it. We then svn copy trunk to a AOO420 branch and start focusing on getting a 4.2.0 GA release out. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Time to push on for 4.2.0
I think it would take about 2 weeks for the most essential items. But sadly my Windows build is crashing on startup and my FreeBSD build is crashing during the build in main/offapi due to some kind of memory bug in idlc (either due to changes in FreeBSD or corruption of my system files), so sadly I first need a few days to investigate and possibly reinstall my setups. I'll keep you updated. On Thu, Apr 12, 2018 at 4:11 PM, Jim Jagielski wrote: > +1 from me. After the below would be a good time to create > the 4.2.0-dev branch from trunk. > > Do you have a timeframe for the below? > > > On Apr 10, 2018, at 9:26 PM, Damjan Jovanovic wrote: > > > > Hi > > > > Before we start on 4.2.0 I would like to finish off porting one final > > module, main/jvmfwk, to gbuild. Then I'll take a break from the build > > changes, and would like to contribute these improvements: > > > > * Overhaul our Java support. Support newer Java versions. Enhance Java > > detection on *nix, adding OpenJDK and matching on prefixes (like openjdk* > > for FreeBSD, eg. /usr/local/openjdk7, /usr/local/openjdk8) instead of > fixed > > strings such as "jdk". Look in /usr/lib too on 64 bit Linux instead of > the > > RedHat-only /usr/lib64. Accelerate Java autodetection by resolving > symbolic > > links and caching results to avoid the slowness of multiple unnecessary > > checks of the same Java directory through different symlinks. > > * GStreamer 0.1 and 1.0. > > * Audit the new SDBC-JDBC bridge and ensure it's 100% compatible with the > > old one. > > * Library naming and symbol versioning audit of all libraries against > 4.1.x. > > * Run all tests against 4.1.x and trunk, and fix the regressions. > > * Full PostgreSQL support (views, indexes, users, groups, GUI dialogs) if > > there is time. > > * Get the Mediawiki plugin working again, if there is time. > > > > > > On Tue, Apr 10, 2018 at 2:54 PM, Jim Jagielski wrote: > > > >> We have still not yet made any strategic determination... We have > >> a possible scenario where gstreamer can be built regardless of > >> what version the build system has in place, but, afaict, that has > >> not yet been folded in. > >> > >> My suggestion would be that that gets committed ASAP so we > >> can test it. We then svn copy trunk to a AOO420 branch and > >> start focusing on getting a 4.2.0 GA release out. > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Time to push on for 4.2.0
+1 from me. After the below would be a good time to create the 4.2.0-dev branch from trunk. Do you have a timeframe for the below? > On Apr 10, 2018, at 9:26 PM, Damjan Jovanovic wrote: > > Hi > > Before we start on 4.2.0 I would like to finish off porting one final > module, main/jvmfwk, to gbuild. Then I'll take a break from the build > changes, and would like to contribute these improvements: > > * Overhaul our Java support. Support newer Java versions. Enhance Java > detection on *nix, adding OpenJDK and matching on prefixes (like openjdk* > for FreeBSD, eg. /usr/local/openjdk7, /usr/local/openjdk8) instead of fixed > strings such as "jdk". Look in /usr/lib too on 64 bit Linux instead of the > RedHat-only /usr/lib64. Accelerate Java autodetection by resolving symbolic > links and caching results to avoid the slowness of multiple unnecessary > checks of the same Java directory through different symlinks. > * GStreamer 0.1 and 1.0. > * Audit the new SDBC-JDBC bridge and ensure it's 100% compatible with the > old one. > * Library naming and symbol versioning audit of all libraries against 4.1.x. > * Run all tests against 4.1.x and trunk, and fix the regressions. > * Full PostgreSQL support (views, indexes, users, groups, GUI dialogs) if > there is time. > * Get the Mediawiki plugin working again, if there is time. > > > On Tue, Apr 10, 2018 at 2:54 PM, Jim Jagielski wrote: > >> We have still not yet made any strategic determination... We have >> a possible scenario where gstreamer can be built regardless of >> what version the build system has in place, but, afaict, that has >> not yet been folded in. >> >> My suggestion would be that that gets committed ASAP so we >> can test it. We then svn copy trunk to a AOO420 branch and >> start focusing on getting a 4.2.0 GA release out. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
For the trunk->4.2.0 we can do what we do for Apache httpd. Create a STATUS file which lists, via SVN commit revisions, what backports are proposed to apply from trunk to the 4.2.0 branch. Once 3 +1 votes are cast on the backport request, they get committed to the branch. Basically, trunk remains CTR whereas the branch becomes RTC using a STATUS file as the backport tracker. > On Apr 10, 2018, at 4:43 PM, Marcus wrote: > > Am 10.04.2018 um 14:54 schrieb Jim Jagielski: >> We have still not yet made any strategic determination... We have >> a possible scenario where gstreamer can be built regardless of >> what version the build system has in place, but, afaict, that has >> not yet been folded in. >> My suggestion would be that that gets committed ASAP so we >> can test it. We then svn copy trunk to a AOO420 branch and >> start focusing on getting a 4.2.0 GA release out. > > thanks for the reminder. > > I also think it's time to start with splitting from the continued > developement and make a branch for 4.2.0. > > The advantage is that we can start to create a stable code base - at the > moment at least for building, later on also for the code quality. > > The disadvantage is that we then need to deal with merging code snippets to > trunk *and* 420_branch. But also at a later time this has to be done anyway - > so not really a disadvantage. > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Hi Before we start on 4.2.0 I would like to finish off porting one final module, main/jvmfwk, to gbuild. Then I'll take a break from the build changes, and would like to contribute these improvements: * Overhaul our Java support. Support newer Java versions. Enhance Java detection on *nix, adding OpenJDK and matching on prefixes (like openjdk* for FreeBSD, eg. /usr/local/openjdk7, /usr/local/openjdk8) instead of fixed strings such as "jdk". Look in /usr/lib too on 64 bit Linux instead of the RedHat-only /usr/lib64. Accelerate Java autodetection by resolving symbolic links and caching results to avoid the slowness of multiple unnecessary checks of the same Java directory through different symlinks. * GStreamer 0.1 and 1.0. * Audit the new SDBC-JDBC bridge and ensure it's 100% compatible with the old one. * Library naming and symbol versioning audit of all libraries against 4.1.x. * Run all tests against 4.1.x and trunk, and fix the regressions. * Full PostgreSQL support (views, indexes, users, groups, GUI dialogs) if there is time. * Get the Mediawiki plugin working again, if there is time. On Tue, Apr 10, 2018 at 2:54 PM, Jim Jagielski wrote: > We have still not yet made any strategic determination... We have > a possible scenario where gstreamer can be built regardless of > what version the build system has in place, but, afaict, that has > not yet been folded in. > > My suggestion would be that that gets committed ASAP so we > can test it. We then svn copy trunk to a AOO420 branch and > start focusing on getting a 4.2.0 GA release out. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Time to push on for 4.2.0
Am 10.04.2018 um 14:54 schrieb Jim Jagielski: We have still not yet made any strategic determination... We have a possible scenario where gstreamer can be built regardless of what version the build system has in place, but, afaict, that has not yet been folded in. My suggestion would be that that gets committed ASAP so we can test it. We then svn copy trunk to a AOO420 branch and start focusing on getting a 4.2.0 GA release out. thanks for the reminder. I also think it's time to start with splitting from the continued developement and make a branch for 4.2.0. The advantage is that we can start to create a stable code base - at the moment at least for building, later on also for the code quality. The disadvantage is that we then need to deal with merging code snippets to trunk *and* 420_branch. But also at a later time this has to be done anyway - so not really a disadvantage. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Am 10.04.2018 um 14:54 schrieb Jim Jagielski: > We have still not yet made any strategic determination... We have > a possible scenario where gstreamer can be built regardless of > what version the build system has in place, but, afaict, that has > not yet been folded in. > > My suggestion would be that that gets committed ASAP so we > can test it. We then svn copy trunk to a AOO420 branch and > start focusing on getting a 4.2.0 GA release out. +1 Matthias > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
