View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010166 | Taler | deployment and operations | public | 2025-07-09 01:25 | 2025-07-09 08:58 |
| Reporter | Florian Dold | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Product Version | 1.0 | ||||
| Target 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 | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-07-09 01:25 | Florian Dold | New Issue | |
| 2025-07-09 08:57 | Christian Grothoff | Tag Attached: vivy | |
| 2025-07-09 08:58 | Christian Grothoff | Severity | minor => feature |
| 2025-07-09 08:58 | Christian Grothoff | Status | new => confirmed |
| 2025-07-09 08:58 | Christian Grothoff | Product Version | => 1.0 |
