[
https://issues.apache.org/jira/browse/MESOS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177472#comment-14177472
]
Niklas Quarfot Nielsen commented on MESOS-1836:
-----------------------------------------------
The module system has versioning (which we also need to keep track of and
advise an upgrading guide similar to how we do between releases). The first
couple of versions will be experimental, but think this is captured well enough
if we keep a module version table, for example:
||Module API Version||Changes||Notes||
|1|Initial implementation of Module sub system|**NOTE:** Experimental feature |
|...|...|...|
> Denote module API as experimental
> ---------------------------------
>
> Key: MESOS-1836
> URL: https://issues.apache.org/jira/browse/MESOS-1836
> Project: Mesos
> Issue Type: Task
> Reporter: Kapil Arya
> Priority: Minor
>
> There should be some notion to inform the module writer of the fact that the
> module API could change. It's not limited to the macros/functions exposed
> via module.hpp, but can also include the module base classes such as
> Isolator, Allocator, and Authenticator. For example, the foo and bar methods
> in TestModule should be tagged "experimental" to show that it can change at a
> later point in time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
