1.0 Release

[novopl]

Plan

Use the tool across many projects and wait until it matures to the point where changes do not have to be introduced often. Once that happens prepare prepare the code base for 1.0 release.

What needs to be done

• Semantic versioning. This should be in place for at a few pre-release versions so there's no hickups once 1.0 hits.

• Documentation. Both for users and developers

  • Code
  • CLI Help for Commands
  • User Guides
  • Developer Guides

• Testing. I'm not yet sure how to do this in a smart way since peltak is mostly a thin layer on top of many third party tools. Leaning towards creating a set of template peltak projects for tests and the tests just running the commands in those directories. scaffy could be used to quickly generate a clean project directory for each test.

  • Core
  • Commands

• Extensibility. The tool should be easily extensible through installing extra packages. The user is responsible for importing the selected commands into his project through pelconf.yaml.

[novopl]

We can put this description into the project description and not clutter the board.