On 01/09/2017 08:24 PM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: > I prefer such notes to be as close to the code as possible. > https://git.opendaylight.org/gerrit/#/c/50140/1/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf
Well, this applies to any and all configuration in the broad sense -- should all our files contain such notices? For consistency sake, will those .sh files pointed to contain pointers back to akka.conf, instructing people to update the reference, should those scripts ever move? I mean really, this is integration/distribution making API-level assumptions about resources in its upstream. I do not believe our current inter-project API contract covers those -- but perhaps it should. Hence it makes sense to mark akka.conf as an API-level contract, so that our usual inter-project API-change workflows apply. It would also be nice to know what sorts of similar assumptions is making on other non-API resources... Bye, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
