The structure will follow the same principle as the one used for the Gasell project with a 3 tiered system.

Here are some examples of initial versions leading up to version 1.0.0 which will be our first "go live" release:

  • 0.1.0 - Basic structure with the possibility to create a batch of invoices
  • 0.2.0 - Basic invoice printing service
  • 0.3.0 - Simple GUI added to view invoices
  • ...
  • ...

GitHub

What would be added here is a description somewhere of a release "code name".

The code name is there to make it more "fun" but also to make it easier to talk about a specific major version for every person affected by the project. Names stick with people easier than numbers.

An example of the release structure

  • Main release: 1.0.0 (code name "Corny Flamingo")
    • Sub release: 1.1.0
      • Patch: 1.1.1

Code name rules

code name = "{State of} {Animal}". Examples:

  • Angry Pommeranian
  • Blue Corgy
  • Sleeping Bumblebee

Jira

The version naming convention must be different than from the one used in GitHub. This is because EG Flow share the same Project space as the Gasell product. If we use the same naming conventions they would collide somewhere along the way and cause issues.

To solve this we prefix the version with "egflow-".

  • Main release: egflow-1.0.0
    • Sub release: egflow-1.1.0
      • Patch: egflow-1.1.1
  • No labels