After [#3059], delete the "old" repo data structures from repository.py. Check carefully though, some stuff may still be used. The new models is in repo.py. Also identify the mongo collections that are unused so we can drop them.
The scm.new_refresh
setting should become irrelevant after this. Everything should be the "new" logic.
Handled already
Diff:
Related
Tickets:
#3059Diff:
Related
Tickets:
#3059Diff:
Related
Tickets:
#3059allura:cj/3060
forgehg:cj/3060
We can't remove
LastCommitDoc_old
, unfortunately, because we never ran the mass update script and it's still relying on old data.Also, the collections to be removed are:
project-data.last_commit_for
pyforge.repo_object
Both branches merged. Once new ForgeHg package hits pythontree (https://trac.sdot.me/trac/siteops/ticket/54029), bump ForgeHg version to
0.1.15
in requirements-sf.txt.