8000 Figure out how to deal with versioning after migrating off TC · Issue #5 · fuse-open/fuse-studio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Figure out how to deal with versioning after migrating off TC #5
Open
@BeeWarloc

Description

@BeeWarloc

Now that we're migrating off TC we should figure out a new way to handle versioning of builds. Ideally the same method should also be usable for uno and fuselibs repos.

Things to consider:

  • Should we take our version from a tag, or use from VERSION.txt as we do today?
  • Should our snapshots and pre-releases be based on the previous or next version number?
  • Should a local build of release commit X.Y.Z have version number X.Y.Z or X.Y.Z-somesuffix?

If we get our versions from tags I know of at least two alternatives we could use:

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

      0