On Wed, Nov 22, 2017 at 8:48 AM, Dave Fisher <[email protected]> wrote:

> 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 complete? If we were to decide to release it “quickly” what
> needs to be done?
>

​I was happy that I could build 4.2 recently on Linux-32 without issue! WOO
HOO!

Re "new" features...there is quite a backlog of translations, including
items in the Help section that are now about 3 years in arrears until 4.2.0
is out. Likely many other improvements including the recent DB access
glitch that Damjen fixed. Timewise, I think there is a bit more to do for
4.2.0 but probably not much.

Like others, I'd like to see AOO move on to 4.2.0 rather than 4.1.5.

​


>
> Regards,
> Dave
>
> > On Nov 22, 2017, at 8:34 AM, Peter kovacs <[email protected]> wrote:
> >
> > 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 Shanahan <
> [email protected]>:
> >> 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. The downside is that, because of more changes, 4.2.0
> >> has a higher risk of regression. Should 4.2.0 go through field
> >> beta-testing?
> >>
> >> Going to 4.2.0 would simplify my activities. Because of better debug
> >> building and on general principles, I do my debug and fixing in trunk.
> >> I
> >> then have to back port the fixes to the 4.1.x line.
> >>
> >> On 11/22/2017 2:37 AM, Damjan Jovanovic wrote:
> >>> 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 <[email protected]>
> >> 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 testing) at:
> >>>>
> >>>>     http://home.apache.org/~jim/AOO-builds/
> >>>>
> >>>> I've built all langs but have just uploaded: de, en-US, es, fr
> >>>> and ja (for now). Let me know if people want/need others
> >>>> uploaded.
> >>>>
> >>>>
> >> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: [email protected]
> >>>> For additional commands, e-mail: [email protected]
> >>>>
> >>>>
> >>>
> >>
> >> ---
> >> This email has been checked for viruses by AVG.
> >> http://www.avg.com
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>


-- 
----------------------------------------------------------------------
MzK

"Only the truth will save you now."
                         -- Ensei Tankado, "Digital Fortress"

Reply via email to