I'll just go ahead and create a branch. They are cheap. And, at least, we'll have a branch ready in case we need it. If not, no big deal.
> On Jan 21, 2019, at 11:38 AM, Patricia Shanahan <[email protected]> wrote: > > I agree that the focus should be on 4.2.0. However, I strongly favor having a > ready-to-go 4.1.7. Any day, we could encounter a really serious, > must-fix-immediately, security bug. Having as much as possible done ahead of > time will reduce the delay from knowing the fix to end users having the fix. > > On 1/21/2019 8:36 AM, Jim Jagielski wrote: >> Gotcha. I was just thinking that if we had a 4.1.7 branch in a ready-to-go >> stage, if we needed to do another 4.1.x release it would be already there. >> But agree that the focus should be on 4.2.0 >>> On Jan 21, 2019, at 11:25 AM, Rory O'Farrell <[email protected]> wrote: >>> >>> On Mon, 21 Jan 2019 11:12:12 -0500 >>> Jim Jagielski <[email protected]> wrote: >>> >>>> Does it make sense to create a branch of 4.1.7 from 4.1.6...? >>> >>> No, unless for some urgent fix. I think better to continue with 4.2.0, >>> then on to 5.0 >>> >>> 4.2.0 editing OK in Writer (60k word file, book format, no >>> illustrations/tables). A simple spreadsheet working OK; existing Impress >>> presentations displaying, apart from two where slide backgrounds cause >>> crash. Multimedia in new presentations not yet checked. >>> >>> -- >>> Rory O'Farrell <[email protected]> >>> >>> --------------------------------------------------------------------- >>> 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] > > --- > This email has been checked for viruses by AVG. > https://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]
