Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pmodules
  • src
  • Issues
  • #169

Closed
Open
Created Oct 10, 2022 by bliven_s@bliven_s

Use semantic versioning

I suggest transitioning pmodules to use semantic versioning. The current use of release candidate prefixes on the stable line and 1.x.x for the development line is confusing. I suggest that the next stable version be 2.0.0 and from there releases follow standard MAJOR.MINOR.PATCH[-devX] nomenclature.

It might be good to change the git practices too so that the default branch (master) corresponds to the most recent development branch. This way the README and CHANGELOG displayed for the project include the most recent info.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking