jason/nest

Tweak the development FAQ a bit.

2019-02-03, John Bailey
dccb114b2be1
Parents 2ba023209eea
Children 36361c968236
Tweak the development FAQ a bit.
1 files changed, 5 insertions(+), 4 deletions(-)
  • +5 -4
    hugo/content/development/faq.md
    • --- a/hugo/content/development/faq.md Sun Feb 03 20:48:18 2019 -0500
    +++ b/hugo/content/development/faq.md Sun Feb 03 20:58:18 2019 -0500
    @@ -1,6 +1,6 @@
    ---
    title: "FAQ"
    -date: 2019-01-10T22:32:00-06:00
    +date: 2019-02-03T20:57:00-05:00
    anchor: "development-faq"
    ---
    @@ -80,9 +80,10 @@
    **This is already defined elsewhere, we should probably just have a page for it... --grim**
    There are three fields in the version: `major.minor.micro`.
    - * If the `major` is changing, you can break plugins. That means both forward- and backward- compatibility. API can be added or removed or whatever you like.
    - * If only the `minor` is changing, you can break forward compatibility only. You may add API, but you can't remove it. You can mark API as deprecated instead.
    - * If only the `micro` is changing, you can't break the API at all.
    +
    + - If the `major` is changing, you can break plugins. That means both forward- and backward- compatibility. API can be added or removed or whatever you like.
    + - If only the `minor` is changing, you can break forward compatibility only. You may add API, but you can't remove it. You can mark API as deprecated instead.
    + - If only the `micro` is changing, you can't break the API at all.
    ## Headers