Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #8578 Use semantic versioning in artifact-modal
    Actions
    Infos
    #8578
    Joris MASSON (jmasson)
    2016-01-12 10:45
    2015-11-10 10:32
    8711
    Details
    Use semantic versioning in artifact-modal

    As a Tuleap contributor, I want to use semantic versioning to define versions for the artifact-modal so that I updating the modal in all the applications that use it is easier and does not necessitate another commit.

    We could use bower.json to define the artifact-modal version and define a range of versions accepted (e.g. ~1.0.0). That way, every time we release a bug fix (e.g. ~1.0.1), the next build would include the updated modal.

    Agile Dashboard
    Empty
    Empty
    • [x] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Declined
    2016-01-12
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Joris MASSON (jmasson)2016-01-12 10:45
    I think we can abandon this request. See last comment : we need an exact version in order to go back in the project's history, so why bother with version numbers when we're already using git sha-1.
    • Status changed from New to Declined
    • Close date set to 2016-01-12
    User avatar
    Joris MASSON (jmasson)2015-11-16 10:33
    We use git sha-1 instead of versions so that whenever we go back in commits we know the exact version of the modal used at this point. We don't want to display more information when the backend didn't provide it for example.
    I'm not sure we can use semver with this requirement.