Kevin Sweeney created AURORA-110:
------------------------------------
Summary: Introduce "strict mode" for the aurora client
Key: AURORA-110
URL: https://issues.apache.org/jira/browse/AURORA-110
Project: Aurora
Issue Type: Story
Components: Client
Reporter: Kevin Sweeney
Priority: Minor
Right now our deprecation cycles are generally accompanied by printing a
(sometimes ominous) warning message to the screen for a time period, and then
releasing a backwards incompatible client that will cause breakage. Introduce a
"strict mode" for the client that fails rather than warns when a
known-deprecated feature is used.
It's a better user experience than finding out (via a client error) that a
client no longer supports a feature you relied on and would allow us a
predictable-but-fair deprecation cycle - e.g. the "quick fix" is always to
remove the --strict flag. For inspiration see Python's _future_ and gcc's
-Werror.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
