Opened 4 years ago

Closed 4 years ago

#8644 closed defect (fixed)

Pluggable transports bundles need an independent version number

Reported by: dcf Owned by: asn
Priority: Medium Milestone:
Component: Obfuscation/Pluggable transport Version:
Severity: Keywords: flashproxy
Cc: asn, aallai Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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) 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.

Child Tickets

Change History (3)

comment:1 Changed 4 years ago by dcf

I'm kind of liking the pt1, pt2 idea because it means all the information is present in the overall version string when someone pastes that to us.

comment:2 Changed 4 years ago by asn

I think I like the pt1,pt2 idea too.

comment:3 Changed 4 years ago by dcf

Resolution: fixed
Status: newclosed

We have this working now with the "pt1" scheme with #8416.

Note: See TracTickets for help on using tickets.