Re: Relaxed STATUS voting rules for experimental features?

On 12.02.2018 16:00, Daniel Shahaf wrote:
> The shelving functionality is experimental:
>
> /** Shelve a change.
> ⋮
> * @since New in 1.10.
> * @warning EXPERIMENTAL.
> */
> SVN_EXPERIMENTAL
> svn_error_t *
> svn_client_shelve(const char *name,
> const apr_array_header_t *paths,
> svn_depth_t depth,
> const apr_array_header_t *changelists,
> svn_boolean_t keep_local,
> svn_boolean_t dry_run,
> svn_client_ctx_t *ctx,
> apr_pool_t *pool);
>
> Shall we relax the STATUS voting criteria for such features?
>
> Currently they are "three +1's"; we could relax to "two +1's".
>
> WDYT?

Backporting experimental features isn't crucial, surely? Yet if there
are changes in trunk, they _might_ affect other code; in that case, more
eyes is better.

-- Brane
Received on 2018-02-12 23:11:31 CET