Strategies for Github Tagging and Release Management

Let's jump into the world of Git and Release Management Planning! Interesting stuff as I go through some of the things to think about as you add new features and enhancements to an existing project - the Spring Boot Blog Application
In this video, you'll learn:
- How to manage changes in your project with different branches
- How to use Git Tagging
- How to create a release on Github
👉👉Grab the source (on github): t.ly/6SrAa
🔗Grab My Other Products Available:
- Packaging a JavaScript Frontend in Java Spring Boot: t.ly/gaKyT
- Build Your First Web Service with Java Spring Boot: t.ly/iv_84
👋🏻Connect with me:
Twitter: / eyuzwa
🔗Links & References:
- Docker Desktop Client: www.docker.com/
- Start Spring IO: start.spring.io/
===---=== Chapters ===---===
0:00:00 - Introduction
0:00:10 - Overview
0:04:12 - Git Tagging
0:05:12 - Github Repository Web Overview
0:10:34 - Semantic Versioning
0:13:42 - Git Branch
0:13:55 - Git Tag
0:15:54 - Create a Release on Github
0:19:04 - Git Checkout Specific Tag
0:20:04 - Outro
#github #springboot #java

[@wazoowebbytes]

This is intended to be part of a series of videos I'm creating all within the plan to add features and enhancements to the existing Spring Boot Blog application! Hope this is informative!

[@EdFolmi]

Hi Wazoo Web Bytes,
I'm working on a feature for my web app where I aim to implement an upgrade button in the frontend. Essentially, the button's text content should dynamically change to indicate an available upgrade to the newest version. Upon clicking the button, I intend for the application's template to switch to reflect the new version. Do you have any insights or suggestions on how I could approach implementing this feature effectively?
Thanks in advance for your help!

[@wazoowebbytes]

Interesting. I'm not sure what you mean by "application's template" in this context. I'm going to assume it's some update to your frontend (ie. changes to pages or business logic, etc). I guess what I would try out is some kind of version API on your server. When the frontend renders the upgrade button, it makes a call to this version API. If there's an updated version, update the button in the frontend to be "Upgrade Available" (or whatever). Then upon clicking, the "easiest" solution might just be a window.location.reload() - Not sure how your client / server is structured, but hope that helps! Thanks for stopping by!