Am 31.10.2017 um 18:52 schrieb Dave Fisher: >> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan <p...@acm.org> wrote: >> >> I do not know if this is the right choice, but we should include doing both >> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as >> possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade >> service. > I agree this what we need to think about. With the new 4.1.4 route we should > make sure that we can tell the difference between the bad original and the > repaired build. Is the date sufficient or would build number be better? I > really don’t like the idea of people being confused about what they need to > do to fix issues. Right now the message is to downgrade to 4.1.3.
My $ 0.02: The date would be sufficient. A new build number means a new build and I don't like the idea to confuse 95% of our users (Windows and Linux) with a "new" version, where not a single line of code was changed. Rebuild the mac version and make an announcement/press release to let the people know about it. > > I would like to know what Andrea and Matthias think since they have been > working with the upgrade system. macOS update notification (4.1.3 -> 4.1.4) is on hold until this issue is fixed. But people can always download directly from our download page, maybe we should put a notice there? Regards, Matthias > > Regards, > Dave > >> On 10/31/2017 9:30 AM, Dave Fisher wrote: >>> There have been over 1,000,000 downloads of 4.1.4. How many were of the >>> bad Mac version? >>> If we replace then how would those people know to upgrade? >>> This issue makes me think we need to have this be a new version so that we >>> can setup the upgrade service correctly. >>> Regards, >>> Dave >>>> On Oct 31, 2017, at 9:21 AM, Jim Jagielski <j...@jagunet.com> wrote: >>>> >>>> Question: Assuming we have "correction" builds available, >>>> what do we do? Simply replace the online version with >>>> these? >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >>
smime.p7s
Description: S/MIME Cryptographic Signature
