Skip to content

Hardware version should be tagged as a release #3

@smiller6

Description

@smiller6

Revision 2.1 was produced by @beehphy , and has been shown to operate well in testing.

I suggest tagging 71e0d74038f05f68dc1f46546d6cc1ff5eac84f3,
which is the latest commit at this time of writing, as a release v2.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions