A PCB to widen the row spacing of a 2x10 100mil-pitch through-hole connector
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Nathan L. Conrad 31b58f82a5 Add -S argument to release script env command 5 years ago
2x10-dip-adapter.pretty Add layout 5 years ago
.gitignore Add layout 5 years ago
2x10-dip-adapter-cache.lib Capture schematic 5 years ago
2x10-dip-adapter.kicad_pcb Use consistent drawing defaults 5 years ago
2x10-dip-adapter.pro Use consistent drawing defaults 5 years ago
2x10-dip-adapter.sch Remove schematic date 5 years ago
README Improve README style 5 years ago
fp-lib-table Create and assign footprints 5 years ago
plot.py Remove some unnecessary plot.py capabilities 5 years ago
release Add -S argument to release script env command 5 years ago

README

2x10-dip-adapter

A PCB to widen the row spacing of a 2x10 100mil-pitch through-hole connector


DEPENDENCIES

  - KiCad version 5.1.6 for macOS.  Results with previous or subsequent
    versions will likely vary.
  - kipy (https://git.alt-tek.com/alt-tek/kipy) is useful to simplify executing
    scripts with KiCad's Python environment.  It is required to generate board
    plots with plot.py for releases.
  - tea (https://gitea.com/gitea/tea) is required to generate releases.
    Install and write your API token to ~/.config/git.alt-tek.com/api-token.
    Restrict access to your API token by setting its file permissions
    accordingly (i.e. 'chmod 600 ~/.config/git.alt-tek.com/api-token').
  - In order to generate releases, SSH must be configured for git.alt-tek.com
    such that SSH Git commands can be executed without explicitly specifying an
    SSH identity or private key


RELEASING

  1. See above dependencies
  2. Create an annotated Git tag for the release commit using
     "git tag -a v<version> -m 'Version <version>' <commit>" where version is
     the board version in X.Y.Z form and <commit> is the commit hash
     (e.g. "git tag -a v1.2.3 -m 'Version 1.2.3' d15c0cafe")
  3. Push the tag upstream (i.e. 'git push origin tags/v<version>')
  4. Use the release script to build the release and upload it as a draft
     (i.e. './release <version>')
  5. Review the release draft.  If it is ready for pre-release or production,
     publish it.