Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-6105

Determine best approach for versioning in development work in Infusion

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 3.0
    • Release
    • None

    Description

      At the moment it is hard to determine what our "next" version of infusion will be. We just tagged Infusion 2.0. Will the next version be 2.0.1, 2.1, or 3.0. In the past we've updated the version number in the repo to reflect the next version. This also has implications for how our dev releases are versioned, via the fluid-publish module; which currently takes the version from the package.json file and appends -dev.xxxxxxxxxxxxx ( where xxxxxxxxxx refers to the date and commit hash that it was built from ).

      See thread for discussion and proposals: http://fluid.2324889.n4.nabble.com/Infusion-dev-numbering-proposal-tt9838.html

      Attachments

        Activity

          People

            Unassigned Unassigned
            jobara Justin Obara
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: