Skip to content
This repository has been archived by the owner on Aug 1, 2021. It is now read-only.

Need specific version tags #14

Open
coderpatros opened this issue Sep 24, 2019 · 0 comments
Open

Need specific version tags #14

coderpatros opened this issue Sep 24, 2019 · 0 comments

Comments

@coderpatros
Copy link
Owner

Seeking feedback from anyone who has an opinion on this.

There should be more specific version tags. Particularly for the CRS version. But also NGINX and ModSecurity.

I don't want to end up with a major proliferation of tags. Unless, of course, if there is a need for it.

For example NGINX has two minor versions currently being maintained, 1.16 (stable) and 1.17 (mainline). Are people actually interested in having a 1.16 image maintained?

With ModSecurity I'm thinking I'll just track the current major version. Currently 3.2.0.

With OWASP CRS I was going to create images for all versions since 3.1.1. Currently 3.1.1 and 3.2.0.

At the moment I'm leaning towards just major version NGINX, major version ModSecurity, major/minor/patch version of CRS.

i.e. current tags, at time of posting, would be

1-3-3.1 and 1-3-3.1.1 matching NGINX 1.17.3, ModSecurity 3.0.3 and CRS 3.1.1
1-3-3, 1-3-3.2 and 1-3-3.2.0 matching NGINX 1.17.3, ModSecurity 3.0.3 and CRS 3.2.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant