aboutsummaryrefslogtreecommitdiffstats
path: root/docs/automating_vpp_api_flag_day.rst
AgeCommit message (Collapse)AuthorFilesLines
2020-04-20Flag day: requirements for candidatesVratko Polak1-3/+17
Change-Id: I0446263333812a57a8d0f7f288044482bee04a14 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
2020-04-16Flag day doc updateVratko Polak1-219/+241
+ Include naming section. + Accomodate for the current usage: + Deactivating change can be uploaded late. + Nect activating change can be squashed there. - Jira tickets and e-mail notifications still listed as required. + Add links to real changes as examples. + Remove old text related to CRC comparison implementation and some scenarois no longer supported. + No double spaces. Change-Id: I33a574989fdfe81a2c53279fb9336165323a6219 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
2019-09-27Update flag day documentVratko Polak1-16/+81
Prevent false -1 from api-crc job. Add more details on CSIT side of things. Minimize the breakage of trending jobs. Also: Add motivation section explaining why earlier solutions are not good enough. - Needs more polishing. - VPP/CSIT, Committer/Developer can be defined in a separate section. - VPP/CSIT trending and verify jobs can be defined in a separate section. - The main process section should list only steps. - Comments on which jobs are broken/fixed can be moved to a separate section. - Name phases, so progress can be described better than "step 9". - Emphasize that only one API change can be in the process. All other changes need to be rebased (to clear any previous +1) before next cycle starts. Change-Id: Ie64a20db3f4abad3c8cddbf13705ff006e5a6382 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
2019-09-27Proposal to automate VPP-API "Flag Day"Dave Wallace1-0/+224
Change-Id: I7bfce00762017b1aa8fd91ce1c8e4c0b810ee7b7 Signed-off-by: Dave Wallace <dwallacelf@gmail.com>