Hi Jim, Am 03.09.2018 um 23:45 schrieb Jim Jagielski: > For some users, AOO 4.1.6 will be the "last" version of OO that they can use, > since AOO 4.2.x will not provide some community build for older platforms > (eg: CentOS5,...). As such, I think we need to make 4.1.6 as good and as > stable and as useful, with as many patches and fixes, as feasible for those > users.
Definitely! We already have some release blocker asked for. How to proceed? Regards, Matthias > >> On Sep 3, 2018, at 4:49 PM, Matthias Seidel <[email protected]> >> wrote: >> >> Hi Andrea, >> >> Am 03.09.2018 um 22:37 schrieb Andrea Pescetti: >>> Matthias Seidel wrote: >>>> How about this one: >>>> https://bz.apache.org/ooo/show_bug.cgi?id=126736 >>>> It fixes a typo in the build process. >>> This one has zero impact for users and, if 4.1.6 was just a >>> maintenance release and we had regular 4.x major releases, it wouldn't >>> make sense to include fixes like this one. Still, it is zero-risk and >>> (unfortunately) 4.2.0 is taking longer than expected, so I understand >>> if we try to backport some fixes to 4.1.6. No objection. >>> >>> In general, release blockers should be: >>> - important bugfixes for users >>> - important build fixes (e.g., don't break with a new compiler) >>> - important infrastructure fixes (e.g., support newer JRE, or a newer >>> Windows release... just an example) >> This is why I didn't ask for release blocker. ;-) >> >> It is just "nice to have" and another resolved issue that would finally >> find its way into a release. >> There are a lot of them, that do not qualify as "blocker"... >> >> Regards, >> Matthias >> >>> Regards, >>> Andrea. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> <mailto:[email protected]> >>> For additional commands, e-mail: [email protected] >>> <mailto:[email protected]>
smime.p7s
Description: S/MIME Cryptographic Signature
