GetInvolved and Donate Infobar advertising messages were introduced in LO 6.1/6.2. An ESC decision had GetInvolved be removed from 6.1.5 stable. At the same time they requested to "release-build-ize it for 6.2 & 6.3". In other words, developers don't want to see it while they are working on the code.
There was also some talk (bug 120271c2) about making it nice for corporations to have an easy switch to turn the nagware stuff off for their own builds, so worth considering how to accomplish that related task at the same time. Corporations would also want to remove the help-donate and perhaps the help-getinvolved menu options (although hiding those menu items in debug builds probably wouldn't be a good idea).
The 6.1.5 revert can be seen at https://gerrit.libreoffice.org/66158.
Code pointers given by Michael Meeks are
dnl Test whether build target is Release Build
AC_MSG_CHECKING([whether build target is Release Build])
if test "$enable_release_build" = "" -o "$enable_release_build" = "no"; then
This guy - and a quick change to the relevant makefile eg.
./writerfilter/CppunitTest_writerfilter_rtftok.mk: -DDISABLE_CVE_TESTS \
And then clobber the setting in a compile conditional there would be good.
* Pending Action Items:
+ disable popups for release-build only in 6.2/.3
The current wording of ESC minutes is a little mis-leading, since it should only be disabled for development builds.
Original discussion is at https://lists.freedesktop.org/archives/libreoffice/2019-January/081715.html
Moving to NEW...
Dear Justin L,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
No one seems interested in doing this, so might as well close.
https://ask.libreoffice.org/en/question/175907/get-involved-nag-line/ has links to extensions that accomplish basically the same thing.
(In reply to Justin L from comment #4)
> No one seems interested in doing this, so might as well close.
> https://ask.libreoffice.org/en/question/175907/get-involved-nag-line/ has
> links to extensions that accomplish basically the same thing.
OTOH, if you add code pointers to this ticket, we can turn this into an easyhack. Up to you