Skip to content

prepare code for release on pub.dev and tag a release version #9

@willp

Description

@willp

only after I feel comfortable with this ending up in other peoples' apps, and comfortable with my time to be able to support PRs and issues, then after that point, if I feel the code is reasonably stable, but still a bit alpha, cut a tagged release of v0.0.x and publish it to pub.dev.

Personally: then switch my depedency to the pub.dev version instead of a local copy. Also, think about an alternate non-prod channel so I can test fresh code more easily? Or not. Whatever makes sense.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions