29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
---
|
|
tags:
|
|
- Maelstrom
|
|
- "-"
|
|
- notes
|
|
- and
|
|
- questions
|
|
relates-to: "[[Maelstrom - notes and questions]]"
|
|
---
|
|
# Maelstrom - other questions
|
|
- How much time is expected to pass between the submit to Main of a modification and its deployment to production ?
|
|
-
|
|
- How many people should be aware and have to give the go for a fix to be deployed to production ?
|
|
-
|
|
- Why are we watching random delivery jiras ?
|
|
-
|
|
- Use case of a virtual machine or clean environment for testing: had an issue qith the get latest of files recently but didn't see it because all files needed werre already on the devs computer. The bug would have been a blocker in production and could have been avoided if the code could have been tested in e clean production setup.
|
|
-
|
|
- Visibilité sur le développement de la CI/CD en python ?
|
|
- C'est grossièrement dans la roadmap mais pas représenté à proprement parler pour le python. Pas de date de prévue à proprement parler.
|
|
- Rebuild suite à des modifs en python
|
|
- aujourd'hui dans le pire cas (full rebuild pour chaque modif python) mais c'est prévu que Maelstrom soit plus intelligent sur ses
|
|
|
|
|
|
---
|
|
# References
|
|
- https://quanticdream.atlassian.net/browse/QDRD-23897
|
|
- https://quanticdream.atlassian.net/browse/QDRD-25788
|
|
- https://quanticdream.atlassian.net/browse/QDRD-25261 |