Bug 117119 - Enable experimental features by default when build is not built in release configuration
Summary: Enable experimental features by default when build is not built in release co...
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-20 08:02 UTC by Florian Reisinger
Modified: 2018-04-23 07:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Reisinger 2018-04-20 08:02:08 UTC
To better test experimental features, those should be enabled by default in builds without "--disable-release-build" flag.

Apparently the default values are set in an XML configuration file. This configuration file is not preprocessed at the moment.

Why this change?

Experimental features are much better visible for testing.
Comment 1 V Stuart Foote 2018-04-20 14:11:33 UTC
This is a horrible idea. Experimental features are expected to be unstable, or marginally complete. Enabling them for testing is an opt in decision--best controlled as always from the Tools -> Options -> Advanced panel.

Forcing them active would just make daily TB builds unstable and really unsuitable for use--meaning with fewer folks testing by building or downloading. We would have less stability testing and fewer regressions picked up during dev cycle.

So IMHO, simply no.
Comment 2 Jean-Baptiste Faure 2018-04-21 15:59:06 UTC
(In reply to V Stuart Foote from comment #1)
> This is a horrible idea. Experimental features are expected to be unstable,
> or marginally complete. Enabling them for testing is an opt in
> decision--best controlled as always from the Tools -> Options -> Advanced
> panel.
> 
> Forcing them active would just make daily TB builds unstable and really
> unsuitable for use--meaning with fewer folks testing by building or
> downloading. We would have less stability testing and fewer regressions
> picked up during dev cycle.
> 
> So IMHO, simply no.

Agreed. Closing as NotABug.

Best regards. JBF