Code Review / optf / has.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 602f77b) | patch
Use OJSI identifier to document fixed vulnerability 48/96648/1 elalto 5.0.2-ONAP
authorKrzysztof Opasiak <k.opasiak@samsung.com>
Sat, 5 Oct 2019 21:19:42 +0000 (23:19 +0200)
committerKrzysztof Opasiak <k.opasiak@samsung.com>
Sat, 5 Oct 2019 21:19:42 +0000 (23:19 +0200)
commit79bef7f1ca027a1aad11ebdbf8975a216d817b97
tree1100e545740af48369d7992acc49e081e85d80c5tree | snapshot
parent602f77bf2e45936b0cd974788d2b58a5f5e2e397commit | diff
Use OJSI identifier to document fixed vulnerability

It's better to stick to the convention that OJSI ticket should be
mentioned in Fixed Security Issues section to ensure full traceability.

Issue-ID: OJSI-137
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I3549e3853b5acd69df00500106ca35dc4002fe10
docs/sections/release-notes.rst diff | blob | history
Homing and allocation service