Skip to content

Project organization -- version numbers, directory structure, etc. #895

@tggagne

Description

@tggagne

Always interested to learn more about packaging best practices (because I haven't found anyone writing about them), I'm curious

  • how you decide when to change version
  • when is the package version created, before or after the PR merge?
  • what concerns or designs went into the directory structure? It's deeper than I expected
  • what other open-source packages are worth looking at for structure, versioning, etc.?

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