From 60f16b494301ff35ca101f3672a004b70b8807d4 Mon Sep 17 00:00:00 2001 From: boubkerbribri Date: Mon, 22 Jan 2024 10:05:02 +0100 Subject: [PATCH] fix: add directory for each file and move images to each process directory --- content/get-involved/_index.md | 2 +- .../quality-council/processes/_index.md | 2 +- .../_index.md} | 0 .../_index.md} | 56 +++++++++--------- .../img}/Issue_state_flow.jpg | Bin .../_index.md} | 30 +++++----- .../img/pr-management1.png} | Bin .../img/pr-management10.png} | Bin .../img/pr-management11.png} | Bin .../img/pr-management12.png} | Bin .../img/pr-management13.png} | Bin .../img/pr-management14.png} | Bin .../img/pr-management15.png} | Bin .../img/pr-management2.png} | Bin .../img/pr-management3.png} | Bin .../img/pr-management4.png} | Bin .../img/pr-management5.png} | Bin .../img/pr-management6.png} | Bin .../img/pr-management7.png} | Bin .../img/pr-management8.png} | Bin .../img/pr-management9.png} | Bin .../_index.md} | 14 ++--- .../img}/release_manager_img_1.png | Bin .../img}/release_manager_img_19.png | Bin .../img}/release_manager_img_2.png | Bin .../img}/release_manager_img_20.png | Bin .../img}/release_manager_img_21.png | Bin .../img}/release_manager_img_3.png | Bin .../img}/release_manager_img_4.png | Bin 29 files changed, 52 insertions(+), 52 deletions(-) rename content/project-organization/quality-council/processes/{contribute-ui-tests.md => contribute-ui-tests/_index.md} (100%) rename content/project-organization/quality-council/processes/{issue-management.md => issue-management/_index.md} (77%) rename content/project-organization/quality-council/processes/{images => issue-management/img}/Issue_state_flow.jpg (100%) rename content/project-organization/quality-council/processes/{pr-management.md => pr-management/_index.md} (85%) rename content/project-organization/quality-council/processes/{images/readme7.png => pr-management/img/pr-management1.png} (100%) rename content/project-organization/quality-council/processes/{images/readme16.png => pr-management/img/pr-management10.png} (100%) rename content/project-organization/quality-council/processes/{images/readme17.png => pr-management/img/pr-management11.png} (100%) rename content/project-organization/quality-council/processes/{images/readme18.png => pr-management/img/pr-management12.png} (100%) rename content/project-organization/quality-council/processes/{images/readme19.png => pr-management/img/pr-management13.png} (100%) rename content/project-organization/quality-council/processes/{images/readme20.png => pr-management/img/pr-management14.png} (100%) rename content/project-organization/quality-council/processes/{images/readme21.png => pr-management/img/pr-management15.png} (100%) rename content/project-organization/quality-council/processes/{images/readme8.png => pr-management/img/pr-management2.png} (100%) rename content/project-organization/quality-council/processes/{images/readme9.png => pr-management/img/pr-management3.png} (100%) rename content/project-organization/quality-council/processes/{images/readme10.png => pr-management/img/pr-management4.png} (100%) rename content/project-organization/quality-council/processes/{images/readme11.png => pr-management/img/pr-management5.png} (100%) rename content/project-organization/quality-council/processes/{images/readme12.png => pr-management/img/pr-management6.png} (100%) rename content/project-organization/quality-council/processes/{images/readme13.png => pr-management/img/pr-management7.png} (100%) rename content/project-organization/quality-council/processes/{images/readme14.png => pr-management/img/pr-management8.png} (100%) rename content/project-organization/quality-council/processes/{images/readme15.png => pr-management/img/pr-management9.png} (100%) rename content/project-organization/quality-council/processes/{release-manager.md => release-manager/_index.md} (73%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_1.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_19.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_2.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_20.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_21.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_3.png (100%) rename content/project-organization/quality-council/processes/{images => release-manager/img}/release_manager_img_4.png (100%) diff --git a/content/get-involved/_index.md b/content/get-involved/_index.md index 37bae026..de1c6340 100644 --- a/content/get-involved/_index.md +++ b/content/get-involved/_index.md @@ -30,7 +30,7 @@ More information: [How to contribute (DevDocs)][how-to-contribute] [request-feature]: {{< relref "request-features" >}} [review-code]: {{< relref "/maintainers-guide/processes/reviewing-pull-requests.md" >}} [test-code]: {{< relref "/project-organization/quality-council/processes/test-pr-and-branches/" >}} -[issue-gardening]: {{< relref "/project-organization/quality-council/processes/issue-management.md" >}} +[issue-gardening]: {{< relref "/project-organization/quality-council/processes/issue-management/" >}} [slack]: {{< relref "/slack/" >}} [github]: https://github.com/PrestaShop/PrestaShop/ [how-to-contribute]: {{< devdocs "contribute/" >}} diff --git a/content/project-organization/quality-council/processes/_index.md b/content/project-organization/quality-council/processes/_index.md index 3459ab86..b899ae48 100644 --- a/content/project-organization/quality-council/processes/_index.md +++ b/content/project-organization/quality-council/processes/_index.md @@ -12,7 +12,7 @@ title: Processes * [Testing Pull Request](./pr-management) -## Software Testing +## Testing with vagrant * [How to test Pull Requests](./test-pr-and-branches) diff --git a/content/project-organization/quality-council/processes/contribute-ui-tests.md b/content/project-organization/quality-council/processes/contribute-ui-tests/_index.md similarity index 100% rename from content/project-organization/quality-council/processes/contribute-ui-tests.md rename to content/project-organization/quality-council/processes/contribute-ui-tests/_index.md diff --git a/content/project-organization/quality-council/processes/issue-management.md b/content/project-organization/quality-council/processes/issue-management/_index.md similarity index 77% rename from content/project-organization/quality-council/processes/issue-management.md rename to content/project-organization/quality-council/processes/issue-management/_index.md index 9d7d7f7a..b42583fe 100644 --- a/content/project-organization/quality-council/processes/issue-management.md +++ b/content/project-organization/quality-council/processes/issue-management/_index.md @@ -10,17 +10,17 @@ This document details the processes in place for the position of "Issues Manager ## The Issue Manager job -Your job is to **qualify issues** submitted to the GitHub project. Good issues help us discover bugs and provide ideas to improve PrestaShop and the native modules. These are the three questions you must ask yourself: +Your job is to **qualify issues** submitted to the GitHub project. Good issues help us discover bugs and provide ideas to improve PrestaShop and the native modules. These are the three questions you must ask yourself: - **Is the issue valid?** The issue must be a bug report. We only cover the PrestaShop project (Core + native modules). Request for feature should be converted in GitHub Discussions. -- **Has all the needed information been provided?** The issue must be understandable and contain the required information as provided in the issue template, complemented with any other detail needed for reproduction. -- **Can it be reproduced?** An issue can't be fixed if we can't reproduce it. +- **Has all the needed information been provided?** The issue must be understandable and contain the required information as provided in the issue template, complemented with any other detail needed for reproduction. +- **Can it be reproduced?** An issue can't be fixed if we can't reproduce it. Here are some tips: -- **Don't provide free support.** Your job isn't to help the reporter fix their problem, but to determine if the problem is caused by a defect in the software (or in documentation). -- **Be pragmatic about your efforts.** It's the reporter's responsibility to provide the information needed to reproduce the problem in an understandable way. Don't waste your energy doing guesswork or waiting for a response. -- **Don't be a robot either.** Don't take these guidelines to the letter. If the reporter makes an effort, try to be flexible. +- **Don't provide free support.** Your job isn't to help the reporter fix their problem, but to determine if the problem is caused by a defect in the software (or in documentation). +- **Be pragmatic about your efforts.** It's the reporter's responsibility to provide the information needed to reproduce the problem in an understandable way. Don't waste your energy doing guesswork or waiting for a response. +- **Don't be a robot either.** Don't take these guidelines to the letter. If the reporter makes an effort, try to be flexible. ## Issue state & labels @@ -73,13 +73,13 @@ Don’t use the **`develop`** label, try to specify the branch like **`8.1.x`** ### Flow overview -Source: [https://miro.com/app/board/o9J_kwzVdW0=/](https://miro.com/app/board/o9J_kwzVdW0=/) +Issue Flow ## Your routine ### New issues -The first thing to do is to deal with the new issues. This can be done by [filtering out New issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+is%3Aopen+label%3ANew). Each of these issues must be managed according to the issue processing protocol. +The first thing to do is to deal with the new issues. This can be done by [filtering out New issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+is%3Aopen+label%3ANew). Each of these issues must be managed according to the issue processing protocol. {{% notice warning %}} @@ -88,7 +88,7 @@ This step should be repeated regularly during the day, to deal with issues as th ### Issues with the NMI label -The second step is to deal with issues labelled `NMI` (Need More Info) without `Waiting for author` label, which could have been updated by the author or any member of the community. To do this, you have to display the [NMI labeled issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aopen+is%3Aissue+label%3ANMI+-label%3A%22Waiting+for+author%22+-label%3A%22Waiting+for+dev%22+sort%3Aupdated-asc+) without `Waiting for author` and sort them by decreasing date of update. NMI issues are issues where crucial information is missing that only the author can provide, usually details on the reproduction steps. If the author or any member of the community has replied and provided the requested details, the issue will proceed according to the issue handling protocol. +The second step is to deal with issues labelled `NMI` (Need More Info) without `Waiting for author` label, which could have been updated by the author or any member of the community. To do this, you have to display the [NMI labeled issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aopen+is%3Aissue+label%3ANMI+-label%3A%22Waiting+for+author%22+-label%3A%22Waiting+for+dev%22+sort%3Aupdated-asc+) without `Waiting for author` and sort them by decreasing date of update. NMI issues are issues where crucial information is missing that only the author can provide, usually details on the reproduction steps. If the author or any member of the community has replied and provided the requested details, the issue will proceed according to the issue handling protocol. {{% notice warning %}} Make sure you inspect all issues updated in the last few days and not just in the last 24 hours! @@ -96,7 +96,7 @@ Make sure you inspect all issues updated in the last few days and not just in th ### Issues to be closed -Finally, the third step consists in tracing the issues that have not been updated for more than 20 days, and closing them. To do this, you have to [filter by increasing date](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aopen+is%3Aissue+label%3ANMI+label%3A%22Waiting+for+author%22+sort%3Aupdated-asc) and on the `NMI` + `Waiting for author`filter. Steps : +Finally, the third step consists in tracing the issues that have not been updated for more than 20 days, and closing them. To do this, you have to [filter by increasing date](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aopen+is%3Aissue+label%3ANMI+label%3A%22Waiting+for+author%22+sort%3Aupdated-asc) and on the `NMI` + `Waiting for author`filter. Steps : 1. Comment with the "Issue without answer" model 2. Remove the `NMI` label @@ -106,7 +106,7 @@ Finally, the third step consists in tracing the issues that have not been update ### End of the day Take the time to list the issues reproduced and taken into account during the day. -Send an email to [coreteam@prestashop.com](mailto:coreteam@prestashop.com), [support-team@prestashop.com](mailto:support-team@prestashop.com), [qa-core@prestashop.com](mailto:qa-core@prestashop.com) AND [coreproduct@prestashop.com](mailto:coreproduct@prestashop.com) with a brief report, with a list of validated issues (aka taken into account) and duplicated issues and share the same content on Public Slack with **[project-members](https://app.slack.com/client/TTJ6M3GPL/G01D794JQTE)**.  +Send an email to [coreteam@prestashop.com](mailto:coreteam@prestashop.com), [support-team@prestashop.com](mailto:support-team@prestashop.com), [qa-core@prestashop.com](mailto:qa-core@prestashop.com) AND [coreproduct@prestashop.com](mailto:coreproduct@prestashop.com) with a brief report, with a list of validated issues (aka taken into account) and duplicated issues and share the same content on Public Slack with **[project-members](https://app.slack.com/client/TTJ6M3GPL/G01D794JQTE)**. Example: @@ -135,9 +135,9 @@ The handling of issues follows a detailed process. Here are the different steps, **Check that the report is really an issue!** -- *Deprecated - if it's a feature request, redirect to the [appropriate template](https://github.com/PrestaShop/PrestaShop/issues/new?assignees=&labels=Feature%2CNew&template=2_feature_request.yml). (since April 2023)* -- **If it's a question** you're not obliged to answer it. Remember that the issues section is not a Q&A forum and that your job isn't to provide free support. Redirect the reporter to a support plan using the "Issue is a support request" response. -- **If it's something that you think should be described in documentation**, consider pinging the developers or moving the issue to the [docs project](https://github.com/PrestaShop/docs). +- *Deprecated - if it's a feature request, redirect to the [appropriate template](https://github.com/PrestaShop/PrestaShop/issues/new?assignees=&labels=Feature%2CNew&template=2_feature_request.yml). (since April 2023)* +- **If it's a question** you're not obliged to answer it. Remember that the issues section is not a Q&A forum and that your job isn't to provide free support. Redirect the reporter to a support plan using the "Issue is a support request" response. +- **If it's something that you think should be described in documentation**, consider pinging the developers or moving the issue to the [docs project](https://github.com/PrestaShop/docs). - **If it is a clearly incomprehensible request**, close the issue by adding the `Invalid` label and answer using the "Issue not completed" response. ### Issue language @@ -149,12 +149,12 @@ Issues must be written in English. If that’s not the case: ### Issue content -The issue (Bug) must be complete. In particular, all mandatory fields in the [template](https://github.com/PrestaShop/PrestaShop/issues/new?assignees=&labels=Bug%2CNew&template=1_bug_report.yml) must be completed: +The issue (Bug) must be complete. In particular, all mandatory fields in the [template](https://github.com/PrestaShop/PrestaShop/issues/new?assignees=&labels=Bug%2CNew&template=1_bug_report.yml) must be completed: -- **Describe the bug and add screenshots:** full details about the bug. This part represents the "observed behavior" following user manipulations. -- **Expected behavior:** the "behavior expected" by the user, to be opposed to the observed behavior detailed above. This is the nominal behavior of the application. Pay attention to the specifications. -- **Steps to Reproduce:** the steps to reproduce the problem. This is the most important part and must be completed in a comprehensive manner. -- **PrestaShop version(s) where the bug happened:** all affected versions +- **Describe the bug and add screenshots:** full details about the bug. This part represents the "observed behavior" following user manipulations. +- **Expected behavior:** the "behavior expected" by the user, to be opposed to the observed behavior detailed above. This is the nominal behavior of the application. Pay attention to the specifications. +- **Steps to Reproduce:** the steps to reproduce the problem. This is the most important part and must be completed in a comprehensive manner. +- **PrestaShop version(s) where the bug happened:** all affected versions - **PHP version(s) where the bug happened:** PHP version - **If your bug is related to a module, specify its name and its version:** the module name and its version @@ -186,7 +186,7 @@ If a duplicate is found: ### Reproducing the issue -We must be able to reproduce the bug in a controlled environment. You can record your attempt, use a screen recorder (like [Screencastify](https://www.screencastify.com/), a Chrome extension), download it and then upload it on Github, post it in a comment so that the issue’s author can see the steps you used to reproduce their issue, either on the current branch or on develop branch, depending of what the author declared in his issue. +We must be able to reproduce the bug in a controlled environment. You can record your attempt, use a screen recorder (like [Screencastify](https://www.screencastify.com/), a Chrome extension), download it and then upload it on Github, post it in a comment so that the issue’s author can see the steps you used to reproduce their issue, either on the current branch or on develop branch, depending of what the author declared in his issue. #### If the **issue cannot be reproduced** @@ -198,17 +198,17 @@ We were not able to reproduce the issue like the author described, even with all #### If the **issue CAN be reproduced** -Once we have reproduced the issue with all the details given by the author, we need to check if the bug exists in the **next stable PrestaShop version to be released**. +Once we have reproduced the issue with all the details given by the author, we need to check if the bug exists in the **next stable PrestaShop version to be released**. -#### **The issue is not reproduced in the next stable PrestaShop version** +#### **The issue is not reproduced in the next stable PrestaShop version** -That means the issue has since been corrected. So you have to find the PR that fixes the problem (it can be a migration PR, or a PR that fixes something else and fixes the problem by side effect!). We then answer the author to give him the information about the PR that fixes the problem, and tell him to update his version of PrestaShop. The issue is then closed. Add the label "Fixed" and don’t forget to add the milestone. +That means the issue has since been corrected. So you have to find the PR that fixes the problem (it can be a migration PR, or a PR that fixes something else and fixes the problem by side effect!). We then answer the author to give him the information about the PR that fixes the problem, and tell him to update his version of PrestaShop. The issue is then closed. Add the label "Fixed" and don’t forget to add the milestone. -#### **The issue is reproduced in the next stable PrestaShop version** +#### **The issue is reproduced in the next stable PrestaShop version** Now we can say that the report is indeed a bug: we now add the `Verified` label. -Now we have to go back up the chain to find the source of the problem. To do this, test the latest stable version of the previous minor release. +Now we have to go back up the chain to find the source of the problem. To do this, test the latest stable version of the previous minor release. If the issue is reproduced: the bug follows the normal course: go to the next step. @@ -224,7 +224,7 @@ The regression of the develop branch must be placed in the Kanban of the corresp ### Labelling -**This step is critical** cause **labelling** consists on tagging the issue according to its different characteristics and it helps us find a bug when we’re looking for a `duplicate`. The different tags are: +**This step is critical** cause **labelling** consists on tagging the issue according to its different characteristics and it helps us find a bug when we’re looking for a `duplicate`. The different tags are: - Type (`Bug` or `Task`), - [Severity (major, minor, ...)](../../../../get-involved/report-issues/how-issues-are-sorted/) @@ -236,7 +236,7 @@ The regression of the develop branch must be placed in the Kanban of the corresp - Status (NMI, Needs Specs, Ready...) - ... (non-exhaustive list) -A list of labels and their use is [available here](https://docs.google.com/spreadsheets/d/118iqWIkW24Rwn6eY8_7FnPhAacGXwA2RdGPzR_LXvy4/edit#gid=0). +A list of labels and their use is [available here](https://docs.google.com/spreadsheets/d/118iqWIkW24Rwn6eY8_7FnPhAacGXwA2RdGPzR_LXvy4/edit#gid=0). ### Connecting an issue to an EPIC @@ -252,7 +252,7 @@ Note that the product team must be able to understand the bug to be able to clas ### Rewriting the issue -Once all the steps have been completed, the content of the issue should be rewritten if it is unclear, or if the author has clarified in the comments. All necessary information should be available in the body of the issue! It may be necessary to rewrite the title if it is too generic (e.g. "Help! BUG!") or if it does not accurately reflect the bug.Pay special attention to the **reproduction steps** ("how to reproduce")! +Once all the steps have been completed, the content of the issue should be rewritten if it is unclear, or if the author has clarified in the comments. All necessary information should be available in the body of the issue! It may be necessary to rewrite the title if it is too generic (e.g. "Help! BUG!") or if it does not accurately reflect the bug.Pay special attention to the **reproduction steps** ("how to reproduce")! ### Validating the issue diff --git a/content/project-organization/quality-council/processes/images/Issue_state_flow.jpg b/content/project-organization/quality-council/processes/issue-management/img/Issue_state_flow.jpg similarity index 100% rename from content/project-organization/quality-council/processes/images/Issue_state_flow.jpg rename to content/project-organization/quality-council/processes/issue-management/img/Issue_state_flow.jpg diff --git a/content/project-organization/quality-council/processes/pr-management.md b/content/project-organization/quality-council/processes/pr-management/_index.md similarity index 85% rename from content/project-organization/quality-council/processes/pr-management.md rename to content/project-organization/quality-council/processes/pr-management/_index.md index d227ea4d..7d778ec5 100644 --- a/content/project-organization/quality-council/processes/pr-management.md +++ b/content/project-organization/quality-council/processes/pr-management/_index.md @@ -11,7 +11,7 @@ You want to take care of a PR and you don't know how to handle it, or you've sim One of the first things to do when starting a PR is to find out as much as possible about it. To do this, you'll find this table at the start of each PR -![img.png](images/readme7.png) +img.png To begin with, we have the **Branch**, which will be useful for preparing our shop and automated tests. So we can already set up a shop accordingly if we don't already have a shop in this branch. @@ -20,7 +20,7 @@ To do this, go to your terminal and execute the commands below: ℹ️ For your information, we recommend that you put it in the *Computer/var/www/html* folder (this recommendation only applies to Linux users). -![img.png](images/readme8.png) +img.png We can see that in **violet** we've put the "**Branch "** we're interested in and in **brown** the name of our file, which can be modified as we wish. @@ -40,7 +40,7 @@ Now that we have an installed shop in which the issue is still present, you can Once on the issue, all you have to do is scroll down to find the "Steps to reproduce" section and follow the steps one by one, taking the example of our same PR: -![img.png](images/readme9.png) +img.png If the issue has been validated by our testers, (⚠️ any PR that mentions an issue must have this issue validated by the QA, otherwise the PR will not be taken into account) the steps to reproduce must have been reviewed by them and are therefore easily reproducible. @@ -54,7 +54,7 @@ If the issue has been validated by our testers, (⚠️ any PR that mentions an Once we've reproduced the issue, we now need to check that the PR actually fixes the problem. To do this, we first need to install it in our shop. We'll take out the terminal in the **PR_81x** folder and you'll be able to type these commands: -![img.png](images/readme10.png) +img.png ℹ️ prc here is an alias that we set up earlier like this : @@ -68,7 +68,7 @@ For the color code, we always use **violet** for the **Branch** and this time we We can find this **number** in the title of the PR, as you can see. -img.png +img.png All you have to do now is try to reproduce the issue again to see if the PR corrects it correctly. @@ -80,19 +80,19 @@ Now that you've checked that the PR has corrected the issue, you need to make su To find them, go to the Files changed tab: -img.png +img.png You'll then have all the changes made to the PR. To do this, you'll get this view: -img.png +img.png Seen like this, it may seem rather difficult to see the differences and what might be impacted, so we advise you to modify the split view and save. -img.png +img.png You now have a better view of the various modifications, and can read the whole thing. -img.png +img.png No computer skills? But you still need to check that it's not overflowing? There are two things you can do: @@ -112,13 +112,13 @@ Once the PR test has been completed, there are two possible situations: - The PR is valid, it doesn't create any other issue. In this case, we advise you to indicate that it works, to put a video proving it (you may think it's the desired behavior but it's not) and to put the link to the automated tests if you ran them. In your comment, you'll need to select the Approve option before submitting the review. -img.png +img.png - The PR is not valid. In this case, indicate that it doesn't work, put a video showing that it doesn't work and put the link to the automated tests if you ran them (to prove that it brings issues). If the PR corrects the issue but creates others, it is necessary to specify the steps to reproduce the issue(s) caused by the PR, so that the PR author can correct the errors more easily. In your comment, you'll need to select the Comment option before submitting the review. The Request changes option will force the same QA to respond to the same PR, whereas it would be preferable for someone else to test it once the changes have been made. -img.png +img.png As you can see, in both cases, you'll have to provide a video and a link to the automated tests to show your good faith. @@ -130,7 +130,7 @@ If you come across a Module PR, the process remains the same as for a PR (in bro To do this, start by opening your PR: -img.png +img.png We've framed the PR version in **Green** and the "branch "** in **Purple**, represented here by **autoupgrade**. @@ -140,7 +140,7 @@ We're going to perform the same operations from the beginning to step 3 So we're going to run a special command in the terminal linked to our shop folder: -img.png +img.png ℹ️ If your module includes a .json package, you need to add this command line for your module to function correctly @@ -162,8 +162,8 @@ For your information ℹ️: If you still can't install the module PR, you'll probably find some hint in its *readme*. -img.png +img.png Click on the **branch** link then scroll down and you'll find an Installation section: -img.png +img.png diff --git a/content/project-organization/quality-council/processes/images/readme7.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management1.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme7.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management1.png diff --git a/content/project-organization/quality-council/processes/images/readme16.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management10.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme16.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management10.png diff --git a/content/project-organization/quality-council/processes/images/readme17.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management11.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme17.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management11.png diff --git a/content/project-organization/quality-council/processes/images/readme18.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management12.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme18.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management12.png diff --git a/content/project-organization/quality-council/processes/images/readme19.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management13.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme19.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management13.png diff --git a/content/project-organization/quality-council/processes/images/readme20.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management14.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme20.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management14.png diff --git a/content/project-organization/quality-council/processes/images/readme21.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management15.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme21.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management15.png diff --git a/content/project-organization/quality-council/processes/images/readme8.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management2.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme8.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management2.png diff --git a/content/project-organization/quality-council/processes/images/readme9.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management3.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme9.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management3.png diff --git a/content/project-organization/quality-council/processes/images/readme10.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management4.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme10.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management4.png diff --git a/content/project-organization/quality-council/processes/images/readme11.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management5.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme11.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management5.png diff --git a/content/project-organization/quality-council/processes/images/readme12.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management6.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme12.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management6.png diff --git a/content/project-organization/quality-council/processes/images/readme13.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management7.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme13.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management7.png diff --git a/content/project-organization/quality-council/processes/images/readme14.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management8.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme14.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management8.png diff --git a/content/project-organization/quality-council/processes/images/readme15.png b/content/project-organization/quality-council/processes/pr-management/img/pr-management9.png similarity index 100% rename from content/project-organization/quality-council/processes/images/readme15.png rename to content/project-organization/quality-council/processes/pr-management/img/pr-management9.png diff --git a/content/project-organization/quality-council/processes/release-manager.md b/content/project-organization/quality-council/processes/release-manager/_index.md similarity index 73% rename from content/project-organization/quality-council/processes/release-manager.md rename to content/project-organization/quality-council/processes/release-manager/_index.md index 28a74785..36409db5 100644 --- a/content/project-organization/quality-council/processes/release-manager.md +++ b/content/project-organization/quality-council/processes/release-manager/_index.md @@ -18,20 +18,20 @@ To do this, simply : 1. Go to Prestashop Pull requests: -Pull request +Pull request 2. Click on Milestones -Milestones +Milestones 3. Click on the version you require (for this example, it will be 1.7.8.9) -Version +Version 4. Click on Closed (these are the merged PRs for the selected version) -Closed +Closed You now have the list of all the PRs merged in your release. It's highly recommended that you check them all to find out what these PRs might affect. @@ -47,15 +47,15 @@ Again, we'll do this in a few steps: 1. Open [Prestashop project](https://build.prestashop-project.org/test-scenarios/) -Closed +Closed 2. Select the various repository affected by the PRs (e.g. a change in product creation) -test repos +test repos 3. Once you've identified the different scenarios that interest you, write them down (or mark them in your notepad). -Tests2 +Tests2 If you've followed all these steps, you should now have your list of test scenarios which should be tested for this release, which you can share with your team members and developers. diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_1.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_1.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_1.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_1.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_19.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_19.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_19.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_19.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_2.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_2.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_2.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_2.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_20.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_20.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_20.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_20.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_21.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_21.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_21.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_21.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_3.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_3.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_3.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_3.png diff --git a/content/project-organization/quality-council/processes/images/release_manager_img_4.png b/content/project-organization/quality-council/processes/release-manager/img/release_manager_img_4.png similarity index 100% rename from content/project-organization/quality-council/processes/images/release_manager_img_4.png rename to content/project-organization/quality-council/processes/release-manager/img/release_manager_img_4.png