Opened 6 months ago

Last modified 3 months ago

#29276 assigned task

Make a release of BridgeDB

Reported by: ahf Owned by: phw
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords:
Cc: cohosh, phw Actual Points:
Parent ID: Points: 5
Reviewer: Sponsor:

Description

As far as we understand here at the hackmeeting in Brussels there is currently no software release of the BridgeDB codebase. We should make a 0.0.1 release (or whatever we decide as initial version number).

Child Tickets

TicketStatusOwnerSummaryComponent
#29594closeddgouletRemove OpenSSL.rand.bytes from codeCircumvention/BridgeDB

Change History (7)

comment:1 Changed 5 months ago by gaba

Owner: sysrqb deleted
Points: 5
Status: newassigned

comment:2 Changed 5 months ago by gaba

Status: assignednew

comment:3 Changed 5 months ago by catalyst

dgoulet says we should update the requirements.txt to the latest available versions, which means fixing #29594 first.

(Do we pin the updated versions, or leave them unpinned?)

comment:4 Changed 5 months ago by catalyst

Owner: set to catalyst
Status: newassigned

comment:5 Changed 3 months ago by phw

Cc: phw added

BridgeDB has a CHANGELOG file that lists changes for each version, and its git repository also has tags for each version; the latest being bridgedb-0.6.9. What else do we need to close this ticket?

comment:6 Changed 3 months ago by phw

Owner: changed from catalyst to phw

Taking this off of catalyst's plate after a brief discussion on IRC.

comment:7 Changed 3 months ago by arma

In an ideal world, the goal here would be to make it so a service admin (i.e. not a bridgedb dev) can take the instructions and the build artifact (tarball, git, etc), and arrive at a correctly deployed bridgedb service. Then somebody can install bridgedb somewhere, maintain it, report bugs back to the developers, upgrade when a new release is ready, etc.

It is maybe overkill at this point because we don't have a separate service admin who can pick it up and do that -- so putting more structure around the release process might be a waste of our precious time for now.

But going through the process once is probably a good idea even if we decide not to put that much formalism around it medium term -- I bet we will find a bunch of surprise changes in the deployed bridgedb service, that you would be unlikely to guess about given what's in git.

Note: See TracTickets for help on using tickets.