Difference between revisions of "Meeting/2021.08.28/Ben, KevinTung"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
== Output == | == Output == | ||
* Boundaries | * Boundaries | ||
* why wiki is good | |||
* cycle time | |||
** use logic model to specify | |||
** refine SC in a smaller sycle time | |||
* Abstract specification -> execute -> have bug -> turn into BC | |||
* Devops is a trial and error process | |||
* PKC IS STANDARDIZING DIFFERENT GRANULARs of TESTING | |||
* error challenge | |||
* logic model specifying causal relationship | |||
** current solution :MEZA | |||
** solution : use linked logic model to specify/ frame in all levels. as there are lots of users , the dynamic process will contribute to BC and SC | |||
* our PKC is the fastest , why? | |||
* docker registry can save registry locally | |||
** need to mount to local |
Revision as of 14:04, 28 August 2021
Start time | 2021-08-28T13:27:22.000Z |
---|---|
End time | 2021-08-28T14:27:22.000Z |
Attendees | @BenKoo, @KevinTung |
Context | Kevin wants to install a new function on the deployment site. Ben thinks we should have a standard workflow to install new software |
Goal | Discuss the DynamicPageList3 extension, Plan the docker deployment workflow |
Criteria | |
Meeting URL |
Output
- Boundaries
- why wiki is good
- cycle time
- use logic model to specify
- refine SC in a smaller sycle time
- Abstract specification -> execute -> have bug -> turn into BC
- Devops is a trial and error process
- PKC IS STANDARDIZING DIFFERENT GRANULARs of TESTING
- error challenge
- logic model specifying causal relationship
- current solution :MEZA
- solution : use linked logic model to specify/ frame in all levels. as there are lots of users , the dynamic process will contribute to BC and SC
- our PKC is the fastest , why?
- docker registry can save registry locally
- need to mount to local