4: Baseline of Known Good State Now that the code compiles, there are no skipped tests, and all tests pass we have a Known Good State. This is the ideal state to begin with for any upgrade or migration.

Let's document our baseline, so we can refer back to it and track out progress.

Create an upgrade notes file.

Open the Editor and create a new file called upgrade-notes.md in the root of the repository.

We're using a .md file because they render nicely in many editors.

Document the current Known Good State.

Add a heading called Initial Baseline

3.1 Upgrade Notes

Initial baseline

• Code compiled successfully
• errors
• Deprecation warnings
  • /Users/newellj/working/spring-boot-2-7-to-3-1-upgrade-source/src/main/java/example/cashcard/SecurityConfig.java: /Users/newellj/working/spring-boot-2-7-to-3-1-upgrade-source/src/main/java/example/cashcard/SecurityConfig.java uses or overrides a deprecated API.
• found disabled/broken test - CashCardApplicationTests#shouldReturnACashCardWhenDataIsSaved
  • fixed broken test and re-enabled Commit all changes, including the new upgrade-notes.md file.

Well, actually, we won't be committing to the repository today in this online, hands-on lab environment.

Instead, we'll create this file on your behalf and update it after each lab in this course. You'll be able to review it as needed.

However, we do recommend a process like the following in your own environment. We understand that you'll have to do whatever is appropriate for your SDLC, but we're confident that you get the idea, here.

Create a branch called "boot3.1-upgrade"

git switch -c "boot3.1-upgrade" Add new and modified files

git add . Commit your changes to your "upgrade" branch with a clear, unambiguous commit message.