Do we need an update to the instructions to clarify that?
On 11/22/2017 12:34 PM, Jim Jagielski wrote:
I think I finally tracked down the problem w/ my Win7/cygwin
build problems. It was subtle.
I kept all my sources in
/home/jim/src/asf/AOO415
that is, it lived under the cygwin
And in honor of the (US) Holiday, I am uploading to
http://home.apache.org/~jim/AOO-builds/
Windows builds for 4.1.5 (just the subset of langs).
This not only allows for tests of 4.1.5 for Windows users
but also that my Windows build setup is (finally) viable!
Cheers!
I think I finally tracked down the problem w/ my Win7/cygwin
build problems. It was subtle.
I kept all my sources in
/home/jim/src/asf/AOO415
that is, it lived under the cygwin file-system.
What I discovered is that the source actually
needs to live under C:, e.g.:
C:/jim/src/asf/AOO415
Am 22.11.2017 um 21:00 schrieb Patricia Shanahan:
I don't think we should wait for more development before releasing fixes
for the 4.1.4 regressions. If 4.2.0 needs another month or so of
development, I'm in favor of releasing 4.1.5 as soon as we can get the
various bug reports checked against
I don't think we should wait for more development before releasing fixes
for the 4.1.4 regressions. If 4.2.0 needs another month or so of
development, I'm in favor of releasing 4.1.5 as soon as we can get the
various bug reports checked against it.
On a side note, for those living outside the
On Wed, Nov 22, 2017 at 6:48 PM, Dave Fisher wrote:
>
> Regarding 4.2.0. What are the new features and is everything being worked
> into trunk complete? If we were to decide to release it “quickly” what
> needs to be done?
>
I don't recommend releasing 4.2.0 immediately;
Hallo Michael,
Die OpenRheinRuhr lag ja von Köln aus sozusagen auf dem Rückweg für mich.
Danke nochmal für die aufschlussreichen Gespräche.
Bis zur FOSDEM habe ich dann auch den neuen Demo-PC fertig und an euch
versandt.
Gruß, Matthias
Am 20.11.2017 um 10:43 schrieb Dr. Michael Stehmann:
>
We have regressions in 4.1.4. Until we get a fix out in either 4.2.0 or 4.1.5
we will continue to get bug reports. These will distract our volunteers and
impact our users.
We owe it to our users to be quick.
Regarding 4.2.0. What are the new features and is everything being worked into
trunk
I think to use 4.2.0 directly is causing less regression then to backport a
subset of fixes on the 4.1.x tree and then test for regressions.
If the fix is indeed successfull with the build changes, we should release the
new build, and go on.
Am 22. November 2017 13:05:14 MEZ schrieb Patricia
>
> > >
> > > > > We have buildbots building 4.1.4 every week...
> > >
> > > > > In my opinion that is a waste of electric power and computing
> > > resources
> >
> > > Well, it is important for the release process, but 4.1.4 is out
> > now...
>
Am 22.11.2017 um 15:17 schrieb Pedro Lino:
> Hi Matthias, all
>
>
>> We have buildbots building 4.1.4 every week...
>>
>
> In my opinion that is a waste of electric power and computing resources
Well, it is important for the release process, but 4.1.4 is out now...
>
>
>> Would it make sense to
Hi Matthias, all
> We have buildbots building 4.1.4 every week...
>
In my opinion that is a waste of electric power and computing resources
> Would it make sense to switch them to 4.1.5?
>
That would make a little more sense...
It should be enough to change the Snap buildbots that are
We have buildbots building 4.1.4 every week...
Would it make sense to switch them to 4.1.5?
Regards, Matthias
Am 22.11.2017 um 13:31 schrieb Damjan Jovanovic:
> What's the alternative to going to 4.2.0?
>
> I only test trunk. So it's 4.1.x that lacks testing from me.
>
> We also really should
What's the alternative to going to 4.2.0?
I only test trunk. So it's 4.1.x that lacks testing from me.
We also really should start running the various tests and comparing results
from trunk against 4.1's.
On Wed, Nov 22, 2017 at 2:05 PM, Patricia Shanahan wrote:
> I see
I cannot reproduce the issue with 4.1.5 dev-build.
my system:
Windows 7 Prof.
AOO415m1(Build:9789) - Rev. 1815796 2017-11-21 09:03 - Developer Build
I have attached my test files in Bugzilla:
https://bz.apache.org/ooo/show_bug.cgi?id=127601
Jörg
I see 4.1.5-dev as a device for testing whether a bug is due to a
specific problem. That change is already checked in to the trunk.
We still have to decide whether to go straight to 4.2.0. The upside is,
as Damjam points out, that we need to get the general benefits of 4.2
out in the field.
Thank you, but when are these 4.1.x releases going to stop?
We have so much lined up for 4.2.0.
Damjan
On Mon, Nov 20, 2017 at 5:49 PM, Jim Jagielski wrote:
> I have both macOS and Linux-64bit builds of 4.1.5-dev (HEAD on the
> AOO415 branch) available for fun and games (and
17 matches
Mail list logo