Skip to content

versioning: Figure something out. #30

@JoeGruffins

Description

@JoeGruffins

There are two things going on atm in the repo. One is a dcr module that could be imported by go, which needs a version, and a cgo api that also needs a version. Changes in one may or may not affect the other. Can we have two versions and what should they start at, 0? What's the best way to handle this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions