Skip to content

strategy for QFN packages #148

@eto-

Description

@eto-

Is there a strategy for QFN packages?

More and more components are in the form of QFN and I think an effort in this direction would significantly improve the usability.

There is a PR #99 which is stuck since two years. Is there some particular problem blocking it? May I help getting the PR approved?

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