superduper icon indicating copy to clipboard operation
superduper copied to clipboard

Published 20 hours ago • verified publisher icon superduper-io

Branching strategy

Open blythed opened this issue 11 months ago • 1 comments

  • One branch per minor/ major (?) version.
  • Patches will be merged to this branch
  • Documentation builds on pulls/ pushes to these branches
  • Documentation versions: 0.1, 0.2, etc., latest, stable
  • Documentation docs.superduperdb.com defaults to stable

blythed avatar Mar 20 '24 12:03 blythed

@blythed Why do we need both latest and stable versions ?

My suggestion would be as follows:

  • Latest: This refers to the most recent minor or major release. It's stored on a separate branch and involves synchronization with PyPI, DockerHub, and documentation.
  • Nightly: This refers to the latest commit on the main GitHub branch. It isn't stored on a dedicated branch and may involve synchronization with PyPI and DockerHub, but not with documentation due to its susceptibility to continuous changes.

fnikolai avatar Mar 20 '24 14:03 fnikolai

Duplicate of #2210.

blythed avatar Jun 21 '24 07:06 blythed