roadmap: path to 1.0.0

[talss89]

This issue serves as a planning scratchpad to bring Sprout up to a stable 1.0.0 release.

<0.1.1: For next pre-release

???

<1.0.0: For stable

• test: integration test suite #19
• build: windows
• feature: installer for windows

Backlog / Ideas(?)

• feature?: repo access token management
• feature?: share repo definitions
• feature?: punch-in for user passwords
• feature?: DB anonymisation - out of scope

Wider discussion

Although I made this for WordPress, there's no reason why this approach wouldn't work for other software projects that depend on large content storage.

There are some specialisations for WordPress (DB search replace on site URL for example) that would need to be abstracted away. Other types of project would likely have similar specifics.

Is it worth planning to turn Sprout into a general content seeding and storage tool?

And if so, at what point do we do that?