| 129 | |
| 130 | = Release Management concerns = |
| 131 | |
| 132 | As GENI experimenters and operators start to use GIMI and the code evolves, there are some release management issues that we should consider. |
| 133 | |
| 134 | 1. Code Delivery |
| 135 | * How will updates be delivered to the end users? |
| 136 | * Packages? Tarballs? Repository? |
| 137 | * What should be included in these releases? |
| 138 | * Where these be published? |
| 139 | 2. Versions |
| 140 | * How will releases be named? |
| 141 | * As users report problems and we create tickets, we will need to identify what version of the software was used so the issue can be reproduced and troubleshooted. |
| 142 | * What versions do we need to track? What dependencies do we have? (e.g. OML server 2.8) |
| 143 | 3. Image Updates |
| 144 | * How often will new static images be created? |
| 145 | * How will updates be handled between static image releases? Postboot scripts? |
| 146 | * How does the user identify which image they are running? Can they tell from within the running node? |
| 147 | |