Details
-
Task
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Description
Definition
Migration of GENIVI git source (meta-genivi-demo.git, genivi-demo-platform.git) to GENIVI GitHub.
Tasks
I created meta-genivi-demo in genivi github(https://github.com/GENIVI/meta-genivi-demo) and only moved master branch and tags.
Could we change the meta-genivi-demo and genivi-demo-platform to meta-genivi-dev and genivi-dev-platform?
1. Which commit is meta-genivi-demo's v9.0?
2. We need to point out meta-genivi-demo in genivi-demo-platform.git of
: May I change qemux86-64, raspberrypi2, and porter branch?
3. If #1 and #2 are finished, can I create genivi-demo-platform.git in github?
4. After all components are moving to GENIVI GitHub, meta-genivi-demo's source location should be changed.
5. Change recipes (image name, document, ...)
6. default branch will be qemux86-64 branch in genivi-demo-platform
7. Wiki description pointing to the main pages in this wiki. It has to state clearly that the wiki at Github will not be used. It also has to mention the bug tracker.
Considerations
- Before moving the branches to Github, maintainers need to agree on the new name schema and the usage of the branches/git strategy. Also the usage of tags and which tags will be used.
- These decisions will be socialised through the mailing list in order to here others opinions.
- It needs to be clarified when the policy change will be done and how should be announced since it must be led/coordinated by jeremiah.foster.
Deliveries
1. Move genivi-demo-platform.git and meta-genivi-demo.git
2. Point out GENIVI GitHub(meta-genivi-dev) in genivi-dev-platform
3. Release to mailing list
4. JIRA and Github integration at app level
5. Shortcut to ease the communication Conflience and Github. Instructions: link to the instructions
6. Integration Confluence and Github
7. Change the submission policy at GENIVI: defailt github. Mail still valid since some companies cannot use github
8. Announce the policy change.
9. Change the links from the wiki page GDP in Detail when the rest of the repos from GENIVI projects are created. (
10. Change the readme.md file from [genivi-dev-platform@github] considering it will be the landing page for many people GDP-194
11. Change deployment script to reflect the change to Github GDP-201
Attachments
Issue Links
- blocks
-
GDP-202 Change How to contribute instructions in GDP home page
- Done
- is blocked by
-
GDP-126 New repo/branch structure for GDP: analysis and proof of concept (PoC)
- Done
-
GDP-201 Deployment script: refer to new repos
- Done
-
COM-1 common-api-dbus-runtime.git: Migrate repository to GitHub
- Done
-
COM-2 common-api-dbus-tools.git: Migrate repository to GitHub
- Done
-
COM-3 common-api-runtime.git: Migrate repository to GitHub
- Done
-
COM-4 common-api-tools.git: Migrate repository to GitHub
- Done
-
COM-5 cpp-someip-runtime.git: Migrate repository to GitHub
- Done
-
COM-6 cpp-someip-tools.git: Migrate repository to GitHub
- Done
-
COM-7 vSomeIP.git: Migrate repository to GitHub
- Done
- relates to
-
GDP-197 Change Demo by Development in every wiki page
- Done
-
GDP-291 Improve the critical journey path for GDP users
- Analysis
- mentioned in
-
Page Loading...