What is the deployment plan for...
-
ygg? [Assumption here: any change to any part of ygg deploys the whole of the titan code base.]
-
terminus?
-
site audit?
-
styx?
-
cookbooks[ Jesse went over the deployment plan for the cookbooks last week.] -
Who functions as the release manager for initiatives?
-
Who functions as the release manager for any other deployments?
-
What's the git workflow?
-
How frequently are hotfixes being made? Are they being tracked?
-
How and when are releases tagged?
-
Is there a deployment checklist? How (if so) is it being enforced?
-
Are there any artifacts of releases?
-
What is currently being automated? What is happening manually?
-
Who (if at all) owns the changelog?
- Please explain how development of any part of the system happens locally.
- Please help me visualize One Box.
- What am I missing? [Maybe Michelle draws a picture of the stack and her mental model can be peer evaluated?]
- Is trail being used?
- Anyone using mocks or stubs?
- Anyone building integration tests with third party software?
- What do the canaries look like right now?
- At what point, if at all, are tests being written?
- Are the product owners owning any of the acceptance testing? If so, when? (How are initiatives declared "done"?)
- What is the barrier to using behavior driven testing?
-
What does "technical debt" mean to Pantheon? How is it discussed?
-
When is refactoring advocated for?
-
When is a rewrite advocated for?
-
refactor === engineer led rework and rework === initiative planned rework
- What question should I be asking but am not yet?