Conversation
| with open('public/zcash-change-deployment-pipeline.html', 'w') as f: | ||
| f.write(html_header) | ||
|
|
||
| for issue in tracked_issues.values(): |
There was a problem hiding this comment.
Current limitation: we don't filter out rows where everything is complete. That is intentional for now while we start filling out the DAG with the necessary data, but eventually we'll want to hide rows that are no longer relevant.
There was a problem hiding this comment.
I think it would be useful to sort completed rows by their recency of completion, and then keep a minimum number for each platform and/or all the ones that were completed up to a given time ago.
For example: at least two completed rows for iOS, at least two completed rows for Android, and everything completed in the last 8 days. That would fit well with weekly meetings (8 days so that we don't miss anything that gets completed around the same time as a meeting).
In GitHub's GraphQl API, when an issue was closed is available in its closedAt attribute, documented here: https://docs.github.com/en/graphql/reference/objects#issue
str4d
force-pushed
the
change-deployment-pipeline
branch
from
b78137f to
564764f
Compare
This shows the progress of implementing tracked bugs and features, and deploying them to the mobile SDKs and Zashi apps. Closes #64.
str4d
force-pushed
the
change-deployment-pipeline
branch
from
564764f to
a666c1a
Compare
zashi-pipeline.py
Outdated
| return | ||
|
|
||
| # Release not found in this repo | ||
| f.write('<td>📥</td>') |
There was a problem hiding this comment.
It would be useful for this to link to the list of C-release issues for the repository, so that if a blocking relationship is missing then the correct release issue can be readily found (or created) and the relationship updated.
| f.write('<td>📥</td>') | |
| f.write('<td><a href="https://github.com/{}/labels/C-release">📥</a></td>'.format(repo_id)) |
3 participants
Closes #64.