It would be easy to stay at a pre-1.0 release for years, but people are right to be skeptical of adopting a project that's unwilling to declare that it's stable and reliable. This is a meta-issue to collect the specific tasks that are highest priority in getting to a 1.0 release.
Essential 1.0 tasks.
[ ] Deployment works on all three currently supported platforms, and all three OSes.
[ ] Output is clean and consistent enough for people to show in learning resources.
[ ] Friendly logs/ summaries work for all three platforms.
[ ] Write a stability policy. #214
[ ] Write a "for authors/creators" doc.
[ ] Review open issues and flag any that are critical for a 1.0 release.
[ ] Make a 0.9.0 release that's essentially a 1.0 candidate release, with a set date for making a 1.0 release.
[x] Sort out ability to push more than one project to Fly.
It would be easy to stay at a pre-1.0 release for years, but people are right to be skeptical of adopting a project that's unwilling to declare that it's stable and reliable. This is a meta-issue to collect the specific tasks that are highest priority in getting to a 1.0 release.
Essential 1.0 tasks.