Skip to content

'Release' Branching for CI/CD and Contributions #85

@thehabes

Description

@thehabes

As an Open Source project we want to avoid having branches "compete" for who gets to be the development deployment at https://tinydev.rerum.io/v1/.

We hope for many PRs to come in at once from Open Source contributors.

We imagine a future where TinyNode is a kind of "download and install" package.

A release branching mechanic that helps control when the production and development deployments occur is necessary in order to help the current situation with "competing" PRs and should be forward thinking for the ways in which we imagine making TinyNode code available to the public.

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