djpbessems/Tinkerbell.Sandbox
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Making statement on breaking changes clearer (#32)

Browse Source 
## Description

Documentation

## Why is this needed

This statement is confusing, I needed to log into the community slack to get clarification.

Fixes: #

## How Has This Been Tested?
This is a documentation change and thus will not impact any software in this project.

## How are existing users impacted? What migration steps/scripts do we need?
They are not, newer users may find this a little easier to digest.


## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
This commit is contained in:
mergify[bot] 2021-01-04 23:06:31 +00:00 committed by GitHub
commit 0cb5e79447
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -14,7 +14,7 @@ is running the hood. Sandbox runs a pinned version for all the components via
commit sha. In this way as a user you won't be effected (ideally) from new code commit sha. In this way as a user you won't be effected (ideally) from new code
that will may change a bit how Tinkerbell works. that will may change a bit how Tinkerbell works.
We are keeping the number of bc break as low as possible but in the current We are keeping the number of breaking changes as low as possible but in the current
state they are expected. state they are expected.
## Binary release ## Binary release