Skip to content

branch structure conforming to orientdb #12

@luigidellaquila

Description

@luigidellaquila

OrientDB main repo has a branch structure like following:

  • master: last stable release
  • 2.0.x: hotfix branch for release 2.0
  • 2.1.x: hotfix branch for release 2.1
    ...
  • develop: branch for next (major or minor) release

plus, final releases are tagged with "2.1.0", "2.1.1" etc.

It would be good to have the same branch structure here, to make dependencies clearer.

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