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

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

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

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

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

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

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 >

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

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,

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

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

Time to push on for 4.2.0

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