-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the stabilized BitOps versioning in the docs #278
Conversation
mkdocs.yml
Outdated
- Development: | ||
- Local development: development-local.md | ||
- Versioning: versioning.md | ||
- Custom Images: custom-image.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new page was placed under the Development
category, but I'm open to suggestions if anyone has a better idea for the Versioning
page category.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, I would put it under configuration. Development to me is more about customizing an image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "Configuration" section would work better indeed.
Updated in 50e358b, thanks!
Following the collective effort in the discussions (#203), WIKI and CD work, document the stabilized official BitOps versioning, showing an example with a table and explanation on how images are named and tagged in different scenarios.