I was thinking about this last week when I was working with Configuration as Code[0] and thinking about some of the concerns which I've seen voiced about the "right API for 1.0", especially around Credentials and some other (currently) gnarly syntax use-cases.
As a user of docker-compose, I find their approach for handling the changes of their docker-compose.yml format to be quite elegant[1]. They include a `version: 3` key at the root level of the YAML and then make it clear in their documentation which versions of docker-compose can make use of which versions of their schema. I think this could be helpful for avoiding concerns about the "finality" of a 1.0 release. If the syntax needs to change in the future, just creating a schema version 2, which can be consumed from a 1.1, or 1.2 release of plugin would be very reasonable IMHO. Thought I would share the idea. [0] https://github.com/jenkinsci/configuration-as-code-plugin [1] https://docs.docker.com/compose/compose-file/compose-versioning/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180510201923.GF2935%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
