The intention of the plan is to try out CR handling. Namely preparing a CR, receiving comments, update the CR based on those comments and approve/reject/postpone a CR. The figure below depicts the main steps in way of working that can be different with Gitlab.
@@ -11,6 +9,10 @@ The intention of the plan is to try out CR handling. Namely preparing a CR, rece
## The trial
Interested delegates can login to the 3GPP forge and enter the repository to start playing around with the environment. We think the trial can be open in the sense that delegates can play around without restrictions, however there are a few things which we would highlight hereafter to take into account during the trial. Other options are available and thus this document does not limit what one can do but can give some direction for those new into the tools involved in this trial. For those that would want to get familiar with the git commands and how to perform the steps below via such commands, one can refer to the [Gitlab documentation](https://docs.gitlab.com/user/get_started/).
### Before you start
Your display name shown on your comments, commits, merge requests, etc. in this tool is by default your ETSI-account user ID. Your colleagues in other companies will likely not know your ETSI user ID so therefore it is good to change your display name to your actual name and company affiliation. To do this, you need to go to "Edit Profile" and change your "Full name".
## Provide comments to CRs
On the left side menu, you can click on the option “Merge requests” (or one can directly go to the [link for merge requests](https://forge.3gpp.org/rep/bergstromm/ran2_trial/-/merge_requests)). A list of all available CRs (here called “merge requests”) should appear.
Click in one of the CRs, which should depict the CR overview as below.
