HTM
HTM software can be checked in
https://hevc.hhi.fraunhofer.de/svn/svn_3DVCSoftware/
Therefore for each integrator an own software branch will be created by the software coordinator containing the current anchor version or the version of the previous integrator:
e.g. branches/0.7-mycompany
The branch of the last integrator will become the new release candidate tag.
e.g. tags/0.8rc1
This tag can be cross-check by the group for. If no problems occur the release candidate will become the new tag after 7-days:
e.g. tags/0.8
If reasonable intermediate release candidate tags can be created by the software coordinator.
ATM
An official release of the 3DV-ATM software can be checked out by mpeg3dv SVN users from the following location:
http://mpeg3dv.research.nokia.com/svn/mpeg3dv/trunk/
Following every JCT-3V meeting, software coordinator creates a new branch for the integration of adopted proposals:
http://mpeg3dv.research.nokia.com/svn/mpeg3dv/branches/
(Note: Would be desirable to rename "mpeg3dv" to "jct3v")
Software integrator checks-out the software from integration branch at its turn of integration plan and integrates proposal as it is specified in Section 11.3.
Software integrator communicates a new software version over the email list to the cross-checker and to the software coordinator.
The software coordinator checks-in to the integration branch every new software integration with confirmed cross-check, as it is specified in Section 11.3.
Once the integration plan is completed, the software coordinator cross-check version available in the integration branch and checks-in a new official release of the 3DV-ATM to the http://mpeg3dv.research.nokia.com/svn/mpeg3dv/trunk/.
Dostları ilə paylaş: |