Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8644
Closed (moved) (moved)
Open
Created Apr 05, 2013 by David Fifield@dcf

Pluggable transports bundles need an independent version number

The PT build instructions say to increment the alpha number whenever you make a release using the same upstream plain TBB. This leads to the situation where our second batch of bundles (#8549 (closed)) built from plain 2.4.11-alpha-1 where called 2.4.11-alpha-2. In the meantime, another plain TBB was released, also called 2.4.11-alpha-2.

I propose we append another "Release" number in the same way that RPM packages do: https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag In this scheme, our first bundles built from 2.4.11-alpha-1 would be called 2.4.11-alpha-1-1, and the next bundles built from 2.4.11-alpha-1 would be 2.4.11-alpha-1-2.

I wonder if we should make it a little more clear that the "Release" number belongs to PT bundles using numbers like 2.4.11-alpha-1-pt1 and 2.4.11-alpha-1-pt2.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking