docs: add a security policy document #504
Conversation
tonyandrewmeyer
force-pushed
the
add-security-md
branch
from
5b05380
to
6c69e1f
Compare
|
I'll rebase after #505. |
|
|
||
| ## Supported versions | ||
|
|
||
| Security updates will be released for all major versions that have had releases in the last year, |
There was a problem hiding this comment.
Just to clarify "all major versions" -- given we only have 1.x.y, I guess this means just one security update?
There was a problem hiding this comment.
Yes, plus the ones that Juju needs. The "only for majors" is where we currently landed for ops, so I re-used that here.
We could have a table here listing versions like some projects do, but that seems a pain to maintain. LXD has rules for monthly and LTS releases - we could copy that but have Juju instead of LTS?
(The "what qualifies" section in the LXD one I think would be good here too, but probably after the current modelling work is done).
There was a problem hiding this comment.
I think what you have now is fine -- I just wanted to clarify the intent. Could add a little parenthetical to clarify for others like "(1.x versions)" if you want.
tonyandrewmeyer
force-pushed
the
add-security-md
branch
from
6c69e1f
to
8db7096
Compare
Document the security policy for the Pebble project.
See also SEC0026.