Skip to content

Latest commit

 

History

History
508 lines (350 loc) · 9.75 KB

presentation.md

File metadata and controls

508 lines (350 loc) · 9.75 KB
Error in user YAML: (<unknown>): found character that cannot start any token while scanning for the next token at line 7 column 9
---
marp: true
size: 16:9
theme: gaia
class: lead
backgroundColor: #fff
backgroundImage: url('./assets/images/hero-background.svg')
footer: @gep13
---
<style> @import 'https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.3.0/css/all.min.css' </style>

Let's Ship This Thing! 🚀

By: Gary Ewan Park
drop-shadow height:150px



Agenda

  • What is an issue?
  • What is Semantic Versioning?
  • What branching strategy should I use?
  • What is GitVersion?
  • What is GitReleaseManager?

bg left:33%

What is an

issue


Demo


bg left:33%

...it is the focal point for work undertaken on a particular task/bug/feature in a product release.


bg left:33%

What is

Semantic Versioning


bg left:33%

...a simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules are based on, but not necessarily limited to, pre-existing widespread common practices in use in both closed and open-source software.


The Rules

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes
  • MINOR version when you add functionality in a backwards-compatible manner
  • PATCH version when you make backwards-compatible bug fixes

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.


Examples

  • 0.1.0
  • 0.3.13
  • 1.0.0
  • 0.2.0-alpha.3
  • 0.2.0-alpha.3+Branch.develop.Sha.e6eb071cd30974b80d7e237b85e7729a1d791e1e

bg left:33%

How do you know

when to bump

a version number


Tools


bg left:33%

There is no quick answer 😿

bg left:33%

What

branching strategy

should I use


GitHub Flow


Create a branch


Add commits


Open a Pull Request


Discuss and review your code


Deploy


Merge


GitFlow


bg 40%


bg 15%


bg left:33%

It depends! 🤷


bg left:33%

What is

GitVersion


bg left:33%

...a tool to help you achieve Semantic Versioning on your project.


Demo


bg left:33%

Why do I need

GitVersion


bg 75%


bg 75%


bg 75%


?


bg left:33%

To make version assertion reliable and consistent


bg left:33%

What is

GitReleaseManager


bg left:33%

...a tool that will help create, and manage, a release for your application/product.


Demo


bg left:40%

Gary Ewan Park

Principal Software Engineer
Chocolatey Software, Inc


Questions


Learn More