23022017 » History » Version 24
J. Moringen, 02/23/2017 07:10 PM
1 | 1 | S. Wrede | h1. 23022017 |
---|---|---|---|
2 | 1 | S. Wrede | |
3 | 22 | J. Moringen | {{>TOC}} |
4 | 22 | J. Moringen | |
5 | 23 | J. Moringen | h2. Next Steps |
6 | 1 | S. Wrede | |
7 | 23 | J. Moringen | # Integrate Robert's template changes |
8 | 23 | J. Moringen | # User meeting |
9 | 23 | J. Moringen | #* Collecting use-case |
10 | 23 | J. Moringen | #* What should the individual modes do (e.g. is "ci-deploy" intended as "fast installation" or "continuous integration with installation"?) |
11 | 23 | J. Moringen | #* How adaptable should modes be without requiring the creation of new modes? |
12 | 23 | J. Moringen | # Turn the following feature ideas into a concrete roadmap in a separate meeting after 20.03.2017 |
13 | 23 | J. Moringen | |
14 | 23 | J. Moringen | h2. Feature List |
15 | 22 | J. Moringen | |
16 | 22 | J. Moringen | h3. Template Hierarchies |
17 | 22 | J. Moringen | |
18 | 22 | J. Moringen | h3. Mode-specific Templates Refactoring |
19 | 22 | J. Moringen | |
20 | 22 | J. Moringen | * Remove Symlinks |
21 | 22 | J. Moringen | |
22 | 22 | J. Moringen | h3. Catkin Templates for ROS Workspaces |
23 | 22 | J. Moringen | |
24 | 22 | J. Moringen | h3. YAML Syntax |
25 | 22 | J. Moringen | |
26 | 22 | J. Moringen | * Multi-line strings -> recipes will be valid YAML -> recipe authors can use validating editors |
27 | 22 | J. Moringen | * No escaping in literal strings |
28 | 22 | J. Moringen | * Comments |
29 | 22 | J. Moringen | * Less "Comma-Problems" |
30 | 22 | J. Moringen | |
31 | 22 | J. Moringen | h3. Deployment / Platform Recipes |
32 | 22 | J. Moringen | |
33 | 22 | J. Moringen | * Specify slaves |
34 | 22 | J. Moringen | * Job configuration details (e.g. with or without unit tests) |
35 | 22 | J. Moringen | * OS, CPU, Flags, ... |
36 | 22 | J. Moringen | |
37 | 22 | J. Moringen | h3. Platform Dependency Analysis |
38 | 22 | J. Moringen | |
39 | 22 | J. Moringen | * Provide downloadable pre-computed descriptions for common platforms |
40 | 22 | J. Moringen | |
41 | 22 | J. Moringen | h3. Docker Slaves for Clean Build |
42 | 22 | J. Moringen | |
43 | 22 | J. Moringen | h3. Thorough CMake Analysis |
44 | 22 | J. Moringen | |
45 | 22 | J. Moringen | h3. Revised Architecture |
46 | 22 | J. Moringen | |
47 | 24 | J. Moringen | * Distribution/project Meta-model |
48 | 24 | J. Moringen | ** Hierarchical Distributions |
49 | 24 | J. Moringen | ** Template Versions of Projects |
50 | 24 | J. Moringen | ** Parametrised Project Inclusions |
51 | 24 | J. Moringen | * Dependencies |
52 | 24 | J. Moringen | ** Richer version expressions with logical connectives and relation operators |
53 | 24 | J. Moringen | ** Phase-aware dependencies |
54 | 22 | J. Moringen | |
55 | 22 | J. Moringen | h3. Credentials Store |
56 | 22 | J. Moringen | |
57 | 22 | J. Moringen | h3. Further Provisioning of Analysis Results in Templates |
58 | 22 | J. Moringen | |
59 | 22 | J. Moringen | h3. Avoid Repetitive Warnings for Missing Dependencies |
60 | 22 | J. Moringen | |
61 | 22 | J. Moringen | Group warnings by missing things, not by projects depending on the thing |
62 | 22 | J. Moringen | |
63 | 22 | J. Moringen | h3. 3rd Party Generator Modules |
64 | 22 | J. Moringen | |
65 | 22 | J. Moringen | * Written in other languages |
66 | 22 | J. Moringen | * Maybe include interpreters for e.g. Python, Javascript in the generator? |
67 | 22 | J. Moringen | |
68 | 22 | J. Moringen | h3. GitHub Migration |
69 | 22 | J. Moringen | |
70 | 22 | J. Moringen | * Probably good idea for project and distribution recipes; how about templates? |
71 | 22 | J. Moringen | * Templates as Part of Build Generator? |