Skip to content

Make better release and tagging system #57

@Ulexus

Description

@Ulexus

Meteor has always been tightly-bound to its environment. We need to provide separate tags for the major Meteor release versions. There have generally been major, sweeping changes between what would generally be considered minor version changes (e.g. 1.4 -> 1.5, 1.5 -> 1.6). We want to stay flexible, but we also want to stay current without breaking existing builds.

This means that:

  • we need static image tags from commit hashes
  • we need compatibility tags for Meteor releases (e.g. ulexus/meteor:1.6)
  • we need to figure out whether we should consolidate the build branch or continue to maintain that separately just for the sake of image size... especially considering Docker's new multi-staged build options

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