Fix url i test plan

This commit is contained in:
Søren Louv-Jansen 2019-09-09 16:14:39 +02:00 committed by GitHub
parent 76a62e2714
commit dbc687c8f9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -7,11 +7,11 @@ Everything that is being released in the 7.4 should be tested by someone other t
The first week after feature freeze (FF) all known bugs and blockers will be fixed. The test plan will begin shortly after this (typically one week after FF date)
### Prerequesites
- Every pull request that is merged to 7.x (or backported to 7.4 after FF) must be given the label: `v7.4.0`. [These pull requests](https://github.com/elastic/kibana/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3Av7.4.0+label%3ATeam%3Aapm+-label%3Abackport) will provide the basis of our test plan.
- Immediately before starting the test plan all relevant PRs for the release are selected and the label `in-test-plan` is applied. The "assigned" field will be reset to nobody (read further why)
- Every pull request that is merged to 7.x (or backported to 7.4 after FF) must be given the label: `v7.4.0`. [These pull requests](https://github.com/search?q=user%3Aelastic+is%3Amerged+is%3Apr+author%3Adgieselaar+author%3Aogupte+author%3Aformgeist+author%3Asqren+author%3Asmith++-label%3Abackport+label%3Av7.4.0&type=Issues) will provide the basis of our test plan.
- Immediately before starting the test plan all relevant PRs for the release are selected and the label `apm-test-plan-7.4.0` is applied. The "assigned" field will be reset to nobody (read further why)
### Execution
- [Find the list](https://github.com/elastic/kibana/pulls?q=is%3Apr+label%3Av7.4.0+label%3Ain-test-plan+label%3ATeam%3Aapm+-label%3Atested-after-ff+no%3Aassignee) of unassigned, untested issues in the test plan
- [Find the list](https://github.com/elastic/kibana/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3Av7.4.0+-label%3Atested-after-ff+no%3Aassignee+label%3Aapm-test-plan-7.4.0) of unassigned, untested issues in the test plan
- Assign yourself to an issue as you start testing it to avoid duplicate work
- Testing a PR can have two outcomes:
- It worked as expected: