[PATCH 00/12] Plannings for secure-testing repository migration to git
This *preliminary* patchset for review is for the changes needed after
we would switch from alioth to salsa for the secure-testing repository.
While needing to do the svn to git conversion the opportunity was taken
to rename the repository to security-tracker as the naming
secure-testing was for historical reason when the testing security
support arised.
Important note: Patch to update_lists triggering is defintively to be
reworked, in conjuction with the automatic updates performed on the
security-tracker host itself.
Furthermore there is a yet untouched script (bin/tracker_data.py) which
might need a rewrite to work properly with a git based security-tracker
repository.
Proposed patchset following.
Salvatore Bonaccorso (12):
review-update-needed: Adjust error message to only mention git
checkout
check-new-issues: Do not mention svn command for review process
update-lists: Update lists in data in git checkout
In DLA mode: if git checkout found ask to push changes
Cleanup documentation after move from Alioth to Salsa
tracker service: Refer to the salsa project on the help out section
tracker service: Update references in footer to salsa
Overview page: Reference to the git repository on the salsa gitlab
instance
lts-bts: Reference dla-needed.txt from security-tracker git repository
lts-update-planned template: Reference dla-needed from git repository
report-vuln: Adjust example usage path to report-vuln scirpt
Reference files from security-tracker git repository on security-team
website
Makefile | 2 +-
bin/check-new-issues | 2 +-
bin/gen-DSA | 14 ++++---
bin/lts-bts | 2 +-
bin/report-vuln | 2 +-
bin/review-update-needed | 2 +-
bin/tracker_service.py | 12 +++---
doc/security-team.d.o/index | 6 +--
doc/security-team.d.o/security_tracker | 68 +++++++++++-----------------------
templates/lts-update-planned.txt | 2 +-
10 files changed, 44 insertions(+), 68 deletions(-)
--
2.15.1
Reply to: