fmWorkMate: Make Releasing fmWorkMate easier

[mrwatson-de]

Note: This Issue is under construction and will be added to bit by bit.

Somehow, releasing fmWorkMate is not simple enough to do it easily and often.

What are the problems? (and how can they be solved?)

• Internal & external Tools

  • fmWorkMate is a toolbox of tools comprising,
    • the toolbox itself
    • internal tools, which
      • belong to the fmWorkMate product
      • reside in the fmWorkMate repository
      • share the fmWorkMate license
    • external tools, which
      • can be used separately from the fmWorkMate product
      • reside in their own repositories
      • have their own licences
      • have their own release rhythms
      • have a stronger/weaker integration in fmWorkMate
  • Are you an 'inny' or an 'outy'?
    • Difficult decision
      • For example, fmSetupAssistant is (currently) an 'inny', however is relatively standalone tool, should maybe made an 'outy'?.

• Release / Version

  • Because fmWorkMate is a collection of multiple tools there is no one version number, which reflects 'its' Major/Minor/Patch state

• Changes log

  • The changes log is currently created from the ### Version ### script's comments of ALL tools

• Data

  • Tools must start with their default standard content
  • Since the development versions of the tools get tested / used by me, this poses two challenges
    • Making sure no private data gets left in the tools