|
|
VTM software development workflow should be followed
|
|
|
[https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/wikis/VVC-Software-Development-Workflow](https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/wikis/VVC-Software-Development-Workflow)
|
|
|
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/wikis/VVC-Software-Development-Workflow
|
|
|
|
|
|
It describes the workflow for VTM, ECM software development follows the same process using ECM repository [https://vcgit.hhi.fraunhofer.de/ecm/ECM](https://vcgit.hhi.fraunhofer.de/ecm/ECM), respectively.
|
|
|
It describes the workflow for VTM, ECM software development follows the same process using ECM repository https://vcgit.hhi.fraunhofer.de/ecm/ECM, respectively.
|
|
|
|
|
|
Particularly for the new users, after GitLab account registration ask for internal account by writing an email with your user name to the VTM (not ECM) software coordinators to request conversion to an internal account. |
|
|
\ No newline at end of file |
|
|
Particularly for the new users, after GitLab account registration ask for internal account by writing an email with your user name to the VTM (not ECM) software coordinators to request conversion to an internal account.
|
|
|
|
|
|
### Bug reporting
|
|
|
|
|
|
* All bugs should be filed in the ECM Issues tracker located at https://vcgit.hhi.fraunhofer.de/ecm/ECM/-/issues
|
|
|
* If a fix is available, the fix should be submitted as a merge request. A reference to the merge request should be added to the bug report. |
|
|
\ No newline at end of file |