Planning update
π Planningβ
The past two weeks have been mostly about planning and refining the work for FDM Monster. It has become clearer to me and others that the project needs a cleaner roadmap.
Together with @Dyrant we've been able to formalize the roadmap and shape the work into Github Milestones The result is a development cycle which slightly looks different than what was before:
- a set of specific features are selected for a release (version 1.6.0)
- in a follow-up cycle, bugs are collected, prioritized and fixed (for example 1.6.1, 1.6.2 and so on)
- and then the next cycle: work towards a new release starts (for example 1.7.0 with Klipper support), but also work on documentation, site and overall code quality (administration)