View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010166 | Taler | deployment and operations | public | 2025-07-08 23:25 | 2025-08-31 17:10 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.0 stretch goals | Fixed in Version | 1.0 stretch goals | ||
| Summary | 0010166: set up separate staging apt (rep)repro, document publishing flow | ||||
| Description | We should first push packages to the testing repo. Once they're deployed on our staging systems and have been tested, they should be promoted to stable. Note that the nightly repo is not enough: * builds are done on the public CI machine * it always builds the master branch, thus we can't select exact package versions that we've tested on a staging server | ||||
| Tags | vivy | ||||
| I have now updated the reprepro setup and documented it at https://docs.taler.net/system-administration/reprepro.html However, I did not test a full release cycle, as I've not had a reason to do any packaging. So the next person (Florian or myself) to do a release will have to test that the instructions work. Ideally Florian, as I wrote the instructions and thus I obviously believe I know how to follow them ;-). | |
| I've tested the publishing flow and added some documentation for the taler-pkg tool. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-07-08 23:25 | Florian Dold | New Issue | |
| 2025-07-09 06:57 | Christian Grothoff | Tag Attached: vivy | |
| 2025-07-09 06:58 | Christian Grothoff | Severity | minor => feature |
| 2025-07-09 06:58 | Christian Grothoff | Status | new => implementing |
| 2025-07-09 06:58 | Christian Grothoff | Product Version | => 1.0 |
| 2025-07-12 16:03 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-07-12 16:03 | Christian Grothoff | Status | implementing => assigned |
| 2025-07-12 16:03 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-07-12 16:03 | Christian Grothoff | Status | assigned => implementing |
| 2025-07-22 12:28 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-07-22 12:28 | Christian Grothoff | Status | implementing => assigned |
| 2025-08-05 15:19 | Christian Grothoff | Note Added: 0025626 | |
| 2025-08-05 15:19 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2025-08-20 12:52 | Florian Dold | Status | assigned => informing |
| 2025-08-20 12:52 | Florian Dold | Resolution | open => fixed |
| 2025-08-20 12:52 | Florian Dold | Note Added: 0025663 | |
| 2025-08-31 17:09 | Christian Grothoff | Status | informing => closed |
| 2025-08-31 17:10 | Christian Grothoff | Fixed in Version | => 1.0 stretch goals |