...
- Gerrit to Github Changes
- We have open CRs currently:
- events
- New Filter and Unistall Filter
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-14067 - filter creation & retrieval
- will be resubmitted using github PRSJira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-14068
- New Filter and Unistall Filter
- clean up
- refactor common pattern in integration tests
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-16520 - update to dep 0.5.4
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-16491 - gotools-clean target
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-16519
- refactor common pattern in integration tests
- fab3 api improvements
- fab3 building docs
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-14651 - gas limit to block return values
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-15233 - getblockbynumber omits invalid txs
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-14617
- fab3 building docs
- events
- Which patches can be abandoned and submitted as PR on github afterwards or do we merge all of these in before making the switch
- We have open CRs currently:
- CR Merge Policy
- Due to the size of the project, instead of requiring 2 maintainers to approve a CR we want to simplify to a single non-author maintainer approval
Jira server Hyperledger JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-16649
- Due to the size of the project, instead of requiring 2 maintainers to approve a CR we want to simplify to a single non-author maintainer approval
- CI/CD Migration: The following should be the different steps of the Azure pipeline
As a reference to Azure Pipeline documentation: https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema- dependencies. Some may have predefined tasks in Azure that we can reuse
- basic-checks (format, vendor, license, etc.)
- Unit-tests
- Integration-tests